Rovo Agent issues in Automation Flows

[Fitzgerald_ Jeffrey]

With the recent enhancements in Jira Automation, I have been encountering failures with my existing rules which use Rovo Agents that were previously working fine for weeks.  The error I get in the Audit Logs is:

Unable to render smart values when executing this flow:

Failed to get value for content.url: {{content.url}}

In my prompt, I am passing 2 automation variables - sample prompt:

Create a Release Synopsis from the Release Title and Summary provided:
Release Title: {{releasePageTitle}}
Release Summary: {{releasePageSummary}}

Preserve all information exactly as provided.

Return a single JSON object containing:
{
"releaseSynopsis": ""
}

Originally, I had it as releasePageContent, so I thought that might be confusing the Agent.  But still encountering this same failure in the automation rule.

[Germán Morales]

Hi @Fitzgerald_ Jeffrey

The variable name is not the problem. The flow fails before the prompt reaches the agent because Automation is trying to resolve {{content.url}}. That is a Confluence page or blog smart value, and it does not appear in the prompt you posted.

For this use case, replace Use Rovo agent with the Use Rovo action. All the required context is already supplied through {{releasePageTitle}} and {{releasePageSummary}}, which is what the self-contained action is intended for.

Add “Return only raw JSON, without Markdown code fences” to the prompt. The response will be available as {{rovoResponse}}; to extract the property, use {{jsonStringToObject(rovoResponse).releaseSynopsis}}.

If the custom agent is required:

• Run More actions → Check for errors and add a Log action immediately before it to print both variables.
• Test in a copy of the flow and recreate only the Use Rovo agent step.
• If the error remains, have a global admin export the flow JSON and search for content.url.

If that value is absent from both the editor and the export, the failure is not caused by your prompt. Send Atlassian Support the flow ID, audit-log ID, and export so they can investigate a possible regression in the Rovo action.

[Fitzgerald_ Jeffrey]

Interesting, I don't have an option for "Use Rovo Action" only "Use Agent" and we are on Premium. 

This automation has been working fine for the last 2 months, only this week with the changes that occurred in Global Automation format and navigation did this error start to arise.  I have logged the variables immediately before the Agent Call, as you noted, but both variables were complete as expected.

I will export the flow and do the search for the "content.url".  In the meantime, I am moving the final Agent Step to its own automation flow to narrow the potential issues, so I am calling it via a webhook. 

Appreciate the advice.

[Arkadiusz Wroblewski]

Hello @Fitzgerald_ Jeffrey 

Did it have worked before ?