Triggering an Automation via another Automation should still reveal traces for the triggered Automation #2095
Unanswered
GtwoK
asked this question in
Automations & scripts
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the feature
The traces for when an Automation runs should include instances from when it is triggered via other Automations.
Use cases
I have an automation that runs some action at a certain time each day. That automation can be triggered earlier, via other automations, based on various factors. But, if those secondary automations DO fire, even when the triggered Automation runs there is no relevant trace for that instance. This is annoying when debugging why some of the actions in the primary Automation didnt complete, as there is no trace to check.
The secondary Automations run every X minutes to check if their conditions are met in order to trigger the primary Automation. As such, there are a huge amount of traces for those secondary automations, that I cannot save them all and they get overwritten quite quickly. So when they DO trigger the primary Automation, and it fires, but something goes wrong, there is no way for me to check what happened.
Alternatively, perhaps some ability to save the last X traces that completed (in addition to the last X overall) could help with this.
Current workarounds
No response
Anything else?
No response
Beta Was this translation helpful? Give feedback.
All reactions