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 wr…

Yes, indeed. [image] July 18, 2024 / bento_box Bunch of improvements Changelog 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 …

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.

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)]

[DONE] Have the Notifications tell us which automation triggered a change

Ideas & Features

Chr1sG July 25, 2024, 6:06am 5

Yes, indeed.

Topic		Replies	Views
[DONE] Hyperlink Fibery Automation Rule in History Automations	5	76	September 5, 2024
Link to / show which automation is responsible for updating entity Ideas & Features	0	145	July 10, 2023
Show the triggering entity in rule logs Ideas & Features	0	34	September 5, 2025
Sep 21, 2023 / 🥹 Watch Entity (through tears), AI Search is out of beta, no fixed bugs Changelog	44	1422	September 15, 2024
How to create a comment in a thread view with Step 1 Linked entity Get Help automations	18	789	January 22, 2024

[DONE] Have the Notifications tell us which automation triggered a change

Related topics