# \[DONE\] Have the Notifications tell us which automation triggered a change **URL:** \ **Category:** Ideas & Features\ **Created:** [October 5, 2023, 5:26am UTC](https://community.fibery.io/t/done-have-the-notifications-tell-us-which-automation-triggered-a-change/5245 "2023-10-05T05:26:12Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![JackC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jackc/32/5420_2.png) [@JackC](https://community.fibery.io/u/JackC)\ **Post date:** [October 5, 2023, 5:26am UTC](https://community.fibery.io/t/done-have-the-notifications-tell-us-which-automation-triggered-a-change/5245/1 "2023-10-05T05:26:12Z")
Automations have names. If we could ID which Automation triggered a change it’d be much easier to track down incorrectly functioning automations. Just on the history where it days “Fibery (rule)” add the rule in question so we can backtrack things faster. If a rule is miswritten and is doing the wrong thing it can be painful to track down, but it could be very quick. ---
**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:** [October 5, 2023, 7:18am UTC](https://community.fibery.io/t/done-have-the-notifications-tell-us-which-automation-triggered-a-change/5245/2 "2023-10-05T07:18:08Z")
Hi @JackC I feel your pain. We are aware of the issue, but there are some technical obstacles which have blocked us from fixing this so far. Will keep you posted. ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [February 20, 2024, 6:49am UTC](https://community.fibery.io/t/done-have-the-notifications-tell-us-which-automation-triggered-a-change/5245/3 "2024-02-20T06:49:04Z")
Any update on this? It feels like it would be an easy improvement to an entities history and would be very valuable for many people. Instead of saying “**Fibery (rule)** did this” I wish it said “**Rule (Database: Rule Name)** did this” ![Iteration-1-—-Iteration-Fibery (1)](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/49257761108503754d04186d47fcfcef7d660b74.jpeg) ---
**Author:** ![JackC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jackc/32/5420_2.png) [@JackC](https://community.fibery.io/u/JackC)\ **Post date:** [July 25, 2024, 2:28am UTC](https://community.fibery.io/t/done-have-the-notifications-tell-us-which-automation-triggered-a-change/5245/4 "2024-07-25T02:28:01Z")
Finally solved. \<3 ---
**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:** [July 25, 2024, 6:06am UTC](https://community.fibery.io/t/done-have-the-notifications-tell-us-which-automation-triggered-a-change/5245/5 "2024-07-25T06:06:04Z")
Yes, indeed. > [@July 18, 2024 / bento\_box Bunch of improvements](https://community.fibery.io/t/july-18-2024-bunch-of-improvements/6413): > > For the next couple of months we will mostly work on improvements, including views, entities creation, settings, etc. We are going to streamline many workarounds and improve overall Fibery experience. Here we go! Reactions and entities mentions in inline comments Now you can react to inline comments and mention entities using # shortcut. Specify the exact Rule instead of Fibery (rule) in audit log and entity history Previously, when trying to trace back why a field value was changed … ---
**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:** [July 25, 2024, 6:06am UTC](https://community.fibery.io/t/done-have-the-notifications-tell-us-which-automation-triggered-a-change/5245/6 "2024-07-25T06:06:37Z")