Issue Summary

When a Rovo agent is invoked via the "Use Rovo agent" action in an automation rule, the automation audit log intermittently reports "Agent invocation failed" even though the agent completed successfully and all downstream actions (e.g., Edit issue) applied the expected updates to the work item.

This is a status-reporting bug. The agent's response is valid, the rule continues execution, and all configured field updates are applied correctly. However, the audit log marks the agent step as having errors, which generates a failure notification to the rule owner.

This creates a significant operational burden for customers who rely on automation failure notifications, as they must manually verify each reported failure to determine whether it is genuine or a false positive. In high-volume environments, this can result in dozens of false-failure notifications per day.

Steps to Reproduce

1. Create or use an existing Rovo agent that performs analysis and returns structured data (e.g., a triaging agent that returns JSON with field values).

1. Create an automation rule with the trigger "When request is created" and the action "Use Rovo agent" followed by an "Edit issue" action that maps {{agentResponse.asObject}} values to issue fields.

1. Enable the rule and allow it to process incoming requests over time.

1. Monitor the automation audit log for the rule.

Expected Results

When the Rovo agent completes successfully, and the downstream "Edit issue" action applies all updates correctly, the audit log should report the agent step as successful.

Actual Results

The audit log reports "Agent invocation failed" on the "Use agent" step, even though:

• The agent returned a valid and complete response.

• The rule continued execution past the agent step.

• The downstream "Edit issue" action successfully applied all field updates to the work item.

• The work item history confirms all expected changes were made.

The failure notification is sent to the rule owner, requiring manual verification of each occurrence.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available