Jira Automation Rule: "Aborted" status when calling Rovo Agent inside the rule

Hi,

Our Jira Automation rules are failing with an "Aborted" status specifically when the Rovo Agent component is used.

Has anyone else encountered this? Looking for any advice or confirmation if this is a widespread issue.

Thanks,
Badri Prasath V

3 answers

1 vote

I contacted to Atlassian support, since all my automation rules where Rovo Agents is included started to fail.

Their answer was:

So let Atlassian to do their investigation and fix this issue. :)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Thanks for the update.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

1 vote

Welcome to the community.

Aborted in most time relates to a time-out.

So the rule is running to long, what does the audit log of the rule state?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Hi Marc,

Thanks for the reply.

Yes, the rule ran for more than 5 minutes. But the same rule ran without any issues last week and we didn't make any changes.

Is there and any outage? please refer the discussion comments provided in https://community.atlassian.com/forums/Atlassian-AI-Rovo-articles/Extended-Testing-Window-for-New-Rovo-Agents-Backend-Model-Until/bc-p/3220798#M2112

Regards,

Badri Prasath V