Problem Definition

In Jira automation rules that use Rovo agents, if the backend LLM request is rate-limited, the Rovo agent invocation fails. This failure currently causes the entire automation rule execution to fail.

• Automation rules that depend on Rovo agents are non-deterministic and can fail for transient, recoverable conditions (rate limiting).

Current Behavior

• An automation rule triggers and reaches a step that invokes a Rovo agent.

• The Rovo agent sends a request to the LLM provider.

• If that request is rate-limited, the agent returns a failure.

• The automation rule then fails, and downstream actions are not executed.

• No automatic retry or backoff is applied; the rule simply ends in a failed state.

Suggested Solution

Implement an auto retry system if the agent invocation fails due to rate limiting issues.

Workaround

There's currently no workaround for this. At this time, the recommended next step is to rerun the failed automation rule.