Subject: Rovo Agent fails on Confluence write actions (Create/Edit page) with "No response received"

[Sven Hamelink]

Description:
We are experiencing a persistent issue with a custom Rovo Agent named "//". This agent is designed to assist our employees by answering questions from our Confluence Knowledge Base ("///").

The Goal:
To improve a particular department autonomy, when the agent "//" does not know an answer, it is instructed to log a "Knowledge Gap" by creating a new page (or appending to an existing one) in Confluence. Dit allows our team to identify and fill missing information in the Knowledge Base.

The Problem:
Whenever the agent attempts a write action (either create-page or edit-page):

1. The "Please review" card appears correctly.

2. The user clicks "Confirm selected".

3. The UI shows "Completed 2 steps" but then displays "No response received".

4. Crucially: No page is created or updated in Confluence. The action fails silently in the backend despite the "Completed" status in the chat.

Environment Details:

• Site URL: ///

• Space: ///

• Target Parent Page ID: ////

• User Permissions: The users (including myself) have full "Add" and "Edit" permissions in the space and can manually create pages under the target parent page without issues.

Troubleshooting steps already taken:

1. Switched Tools: We moved from append-content to create-page to rule out timeouts caused by large page sizes.

2. Simplified Content: We removed all complex formatting (tables, macros) and tested with plain text to rule out ADF (Atlassian Document Format) corruption.

3. Verified IDs: Confirmed the Page IDs and Space keys are correct.

4. Location Testing: Tested creating pages both with and without a Parent Page ID.

5. Permission Check: Verified that manual page creation works for the same users.

Request:
Could you please investigate the backend logs for the ActionToolAgent / Rovo integration for our site? It appears there is a disconnect or a timeout occurring between the Rovo action confirmation and the actual Confluence API execution, even though the agent thinks the step is "Completed".

[Rebekka Heilmann _viadee_ · Accepted solution]

Hi @Sven Hamelink - welcome to the Community,

firstly, please note that this is a public forum so do not share internal information or screenshots that is not needed for answering your question. The site url and space name is irrelevant to us but reveils information that may be useful to attackers.
We also don't have access to any backend logs. You would need to contact https://support.atlassian.com/ for that. If Rovo shows up as "free", simply select one of your paid products so the UI doesn't direct you to the Community.

---

Rovo still has issues with creating pages in the correct hierarchy so one thing I'd recommend is trying to have the Agent simply publish a page *anywhere* in the Space (which will most likely be below the homepage). If that works, we can co from there.

[Sven Hamelink]

Hi Rebekka,

Thank you for the quick response and the warning regarding the public nature of this forum. I have redacted the sensitive details.

Regarding your suggestion: I have just performed a side-by-side test to isolate the issue, and the results are very specific:

1. Hierarchy Test: I removed the Parent Page ID from the Agent's instructions as you suggested.
2. Desktop vs. App:
   • Rovo Desktop/Studio: The Agent successfully created the page 'anywhere' in the Space. The action completed without errors.
   • Rovo Mobile App: Using the exact same Agent and the exact same chat session, the action consistently fails with a "No response received" error, and no page is created in Confluence.

This confirms that while the hierarchy bug you mentioned is a factor, there is also a significant runtime/UI timeout issue specific to the Rovo Mobile App that does not occur on Desktop.

Can you help with this or do I need to apply a formal ticket at support Atlassian?

Thanks again for pointing me in the right direction!

[Rebekka Heilmann _viadee_]

I've not got experience with Agents in the Mobile App to be honest. If there is a feedback button in the App somewhere, I'd use that. Otherwise a regular Support Ticket is certainly helpful as they can create feature requests or bug reports on your behalf as well.

[Rebekka Heilmann _viadee_]

I've also directed your question to some people at Atlassian who are currently working at Skills, so hopefully the Create Page skill is improved soon.

[Sven Hamelink]

Thanks for the help Rebekka!