Automation status "No actions performed" even though trigger conditions are met

[Melissa Posselt]

Hi there,

I set up the following automation below. It worked when I first tested it - but then suddenly stopped working and showing the status "No actions performed" in the audit log.

Why could this be and how can I fix it?

I've heard before that automation rules sometimes can run into run time issues, but I don't know much bout that, what might cause it, how to fix it, and if this could even be the case here.

The automation is triggered when a page is published. There is a CQL condition, only running the actions if the page is published under a specific parent. Then, a Rovo agent is asked to draft a response. Afterwards, a new Jira Bug issue is created, with the agent response in the issue description. FInally, a comment is posted under the trigger confluence page, telling the page owner to review the created issue and linking it.

When I initially tested the automation, I had not added the comment action yet - but I somehow cant imagine that this action would have broken the automation.

UPDATE:
After removing the "Add comment" component, the automation is working again. So strange - I've used this component multiple times before. Any ideas why this might be happening?

I am really grateful for any help!

[Tomislav Tobijas]

Hi @Melissa Posselt ,

Can you take a screenshot of the audit log (one entry fully expanded)? 

"No actions performed" in the audit log would usually mean that some conditions are not met (in your case, only there's that one for the parent page). If it went through, even the first part "Use Rovo Agent" should result in at least one action execution 👀

Cheers,
Tobi

[Melissa Posselt]

Sure thing! Here you can see the audit log expanded for bot the last time it worked successfully and the first time "no actions performed". As you can see, the conditions checked both time are exactly the same and passed.

[Tomislav Tobijas]

Thanks @Melissa Posselt !

Yeah... can't say much for this as you can imagine. It would seem that the condition did not pass for some reason, but I'm not sure why. Audit logs don't include that detailed info (although there's a feature request for it).

What you could try to do is add a Log action before and after CQL condition. For example, you can add one before which would include {{page.parent.id}} (to check if in fact it get's parent page correctly), and after the condition, just some log such as "Condition passed".

I'm guessing you're manually creating these pages (or are they created via some webhooks or automation)?
I was thinking in the direction of somehow re-fetching page info (such as parent), but there isn't a re-fetch action in Confluence. Maybe you could also try to use "Delay" action before the condition?

I believe this would be the fastest to debug hands-on, so you could try to reach out to Atlassian Support and grant them data access so they can check what's going on in the background 👀

Cheers,
Tobi