# Rule not working consistently to add and auto-link entity

**URL:** <https://community.fibery.io/t/rule-not-working-consistently-to-add-and-auto-link-entity/7878>\
**Category:** Bugs & Issues\
**Created:** [November 30, 2024, 7:05pm UTC](https://community.fibery.io/t/rule-not-working-consistently-to-add-and-auto-link-entity/7878 "2024-11-30T19:05:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathan](https://avatars.discourse-cdn.com/v4/letter/j/aeb1de/32.png) [@Jonathan](https://community.fibery.io/u/Jonathan)\
**Post date:** [November 30, 2024, 7:05pm UTC](https://community.fibery.io/t/rule-not-working-consistently-to-add-and-auto-link-entity/7878/1 "2024-11-30T19:05:50Z")

</div>

Hello, my rule does not work consistently.

It’s designed to create a new auto-linked entity any time a calendar event is created . It has worked, but it has not been reliable and I would like to know whether this is something I can fix on my end.

Any ideas?

Here is the rule:

 ![Screenshot 2024-11-30 at 10.26.48 AM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/df4922fab76565ab7d60dc51f972eb37e5624400.png)

I added a test event, and this is the resulting entries from Activity Log:

 ![Screenshot 2024-11-30 at 10.25.46 AM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/75947543b12166ba43ab9e9c2121affaac01c810.png)

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 30, 2024, 7:23pm UTC](https://community.fibery.io/t/rule-not-working-consistently-to-add-and-auto-link-entity/7878/2 "2024-11-30T19:23:33Z")

</div>

I think you need to check out the rules for automation logic  
[https://the.fibery.io/@public/User\_Guide/Guide/Automation-execution-logic-332](https://the.fibery.io/@public/User_Guide/Guide/Automation-execution-logic-332)

If the field that is being checked in the filter is getting updated some time after creation, then you will not have determinism about whether the automation actions are executed or not.
