When Using Rovo Agent Confluence Automation to find the new changes in a page Automation failing

[Vikrant Yadav]

Hi Experts,

I need your help in fixing an automation rule.

I have created an automation rule in Confluence. The purpose of this rule is to create a Jira issue whenever changes are made to a Confluence page.

In my automation:

• The trigger is "Page Edited"
• The second action is "Rovo Agent", which is supposed to identify the changes made in the Confluence page and return only those changes
• The third action is "Create Jira Issue"

However, the rule gets stuck at the "Rovo Agent" action. It keeps showing Waiting, and eventually, the rule aborts.

I’m not sure how to fix this. The agent works fine when accessed via the "Ask Rovo" option, but within the automation rule, it remains stuck in the waiting state.

Could you please suggest how to fix this issue?

[Staffan Redelius · Accepted solution]

It is a good idea to log the value of the {{agentResponse}} as suggested by @Marc -Devoteam- You can do this by adding a log-step in the workflow

Sometimes it helps to be explicit on what you want added to the {{agentResponse}} i.e. "compare the current page with the previous version and add the changes to {{agentResponse}} "

Have you been explicit on what the agent should do with the {{agent.Response}} Should it add it be added to the description of the Jira work itemt or only add a link to the page?

Have you added the skill "Create work item" to the agent?

Please update with your findings to help others get better use of Rovo.

Best regards,
/Staffan

[Vikrant Yadav]

Hi @Staffan Redelius 

As you can see in the screenshots below, I have already added {{agentResponse}} in the log action.

However, the agent is not triggering. The automation stops at the agent action and shows the status as "Waiting", and after some time, it gets "Aborted."

I am not sure why the agent is not triggering.

[Staffan Redelius]

Hi @Vikrant Yadav 

Yesterday I set up a similar automation in my own instance just to explore the use case since I found it interesting. 

I can confirm the behaviour, the automation get stuck in "Waiting" and after some time goes to "Aborted"

There has been an active incident affecting Automations when using agents:

Confluence Status - Disrupted Rovo availability for Automation rules

When I tried the automation this morning it worked as expected so no fault on your side. Try again and it will probably work

Best regards,
/Staffan

[Bill Sheboy]

Hi @Vikrant Yadav 

There was a production incident for Rovo-related automation rules for the last several hours, and it appears to have been marked as resolved now:

https://confluence.status.atlassian.com/incidents/4fwvl5sdyz7m

Perhaps try testing your rule now.  Thanks!

Kind regards,
Bill

[Vikrant Yadav]

Thanks @Bill Sheboy  

Yeah it was due to yesterday incident. 

Rule is working fine now. 

No issue in the rule 😊

[Marc -Devoteam-]

Hi @Vikrant Yadav 

This probably relates to the description or behaviour of the agent.

As based on this it's waiting for a response, what is the agent response if you log this in a log action in the rule, use smart value {{agentReponse}}

Based on the agent response the action to create a Jira issue should be activated.

https://support.atlassian.com/rovo/docs/agents-in-automations/ 

[Vikrant Yadav]

Hi @Marc -Devoteam- 

Agent is working when asking the agent from "Ask Rovo" section.

But in Automation rule, it's keep on showing wating and after sometime rule "Aborted", rule stuck at "use Agent" action. 

[Marc -Devoteam-]

Hi @Vikrant Yadav 

On using an agent in an automation rule the agents need to provide a response.

So the agent response is base for further actions in the rule.

I currently don't have any examples at hand, as I'm working on a closed company based machine.

[Vikrant Yadav]

Hi @Marc -Devoteam-  Automation blocked when reaching at Agent action. 

It stuck at "Waiting". 

[Marc -Devoteam-]

Hi @Vikrant Yadav 

This means the agent requires input, so it will not proceed without input.

To use an agent in automation, is quite a different setup of the agent behaviour and description of the agent.

This is an example of  an gent that acts in an automation rule

Description

This agent walks users through creating and evaluating stories for use in an Agile team with context and acceptance criteria.

Behavior

## Role

You are a Product Owner helping engineers and project managers write high-quality Agile user stories, and review its readiness against our Definition of Ready (e.g., clear summary/description, estimates, acceptance criteria, dependencies) 

---

## Purpose

Drives higher standards for work intake by identifying gaps in requirements, traceability, and planning. The agent helps teams avoid rework and delays by ensuring issues are ready before development begins.

You have two tasks:

- You gather the inputs required and create a structured story in Jira according to a team's Definition of Ready (DoR) and standard issue hygiene.

- Check if Jira issues are fully ready for development according to a team's Definition of Ready (DoR) and standard issue hygiene. You generate a scoring table.--- 

## Behavioral Rules

* Never use en or em dashes.

* Before providing co-created answers, always ensure that your response does not embed characters, like the Narrow No-Break Space.

* Always use gender neutral language.

* Write in a direct, personable, casual tone. Not upbeat or exuberant, but straightforward and helpful.

* Use jargon-free, clear language. Clarity is key.

* Use active voice; avoid passive voice. 

* Stay under 50 words per rationale comment.

* Be direct, practical, and slightly formal in tone.

* When possible, use words from the issue summary or description when suggesting improvements.

And more on scenarios and related content that is used, like Confluence for DoR and DoD