We recently migrated from DC to Atlassian cloud. On DC when troubleshooting automation(s) if I clicked on the link in the audit log it took me the component that was associated with the link. Cloud doesn't appear to do that. Is there an easy way, other than counting the components in the log and then counting down the automation, to figure out which component actually fired or errored?
Hello @Dan W
On the cloud side, the easier way to identify which rule errored out would be to go to the 'Global Administration' panel for Automation.
The rule which errors out would have a 'Red Exclamation' mark next to it. You can open the rule and click on 'Audit Log' which opens the logs for that particular rule.
This will help in identifying the exact error and easy troubleshooting. Please refer to the below screenshot for details.
Please share if this helps or if there are any other related questions. Please accept the response if this help in resolving the problem.
While this helps to find the rule that errored it doesn't help find the action that errored. We have some automations that have 20+ statements I have to count the statements in the audit log and then go and count down through the automation to figure out which one errored and to make sure the proper statement is executing. In DC I would click the error in the audit log and it would take me to the action that caused the error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.