Why do the flow audit logs no longer show why it did not trigger or if something is wrong?

[Philip Ng]

I just noticed today my Automation/Flows page has a different look which is fine. But I was looking to see why my automation didn't trigger for an issue, so of course I went to check the audit log. I see the jira issue in the list and it says no actions performed. So, I then click into it, but it no longer shows why it did not process or run thru the automation. The only thing it says is the work item was created which is my trigger. It doesn't seem to show at what point of the automation it failed or doesn't meet the criteria anymore. Is this something new they implemented? Is there any way to switch back to the previous version so I can see that information?

[Bill Sheboy]

Hi @Philip Ng 

I have noticed both the changes in the rule editor UX, and consistency / accuracy problems in the audit logs since the recent changes to allow log exports in the last few days.  (e.g., missing log entries, duplicated work item keys in log, etc.)

Perhaps if we see your specific rule it may help indicate if the changes are the symptom cause or something else.  Please post the following:

• what type of project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution

Kind regards,
Bill

[Germán Morales _ Hiera]

Hi Philip,

I think there are two slightly different cases here:

1. No audit log entry for the work item
If there is no execution entry at all, the flow probably did not trigger. In that case I would check the trigger configuration, trigger filters, project/space scope, and whether the event was caused by another automation flow.

2. Audit log entry exists but says “No actions performed”
That usually means the flow did trigger, but one or more conditions/branches did not match, so it stopped before running actions.

Atlassian’s current automation docs still say that each audit log entry can be expanded to show the details and run time of each step. They also recommend using the audit log as the first debugging step, and using “Log action” or `{{#debug}}...{{/debug}}` when you need more context from smart values.

So I would try:

- Open the automation flow itself, not only the issue activity.
- Go to the flow’s Audit log.
- Expand the specific execution entry.
- Check whether the failed/skipped step is visible there.
- Add temporary “Log action” steps before important conditions to print the values being evaluated.
- If there is no execution at all for that issue, review trigger filters and flow scope.

I have not seen an official documented switch to restore the previous audit log UI. If the expanded execution no longer shows the failed condition details for you, it may be part of the new automation/flow UI rollout or a regression worth raising with Atlassian Support.

Official docs:
https://support.atlassian.com/cloud-automation/docs/what-is-the-automation-audit-log/
https://support.atlassian.com/cloud-automation/docs/debug-an-automation-rule/