Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Rovo Agent unable to copy a page that can be manually copied

Matt Welch
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 3, 2025

We created a Rovo agent and gave it the Copy skill for confluence pages. When asked to perform a copy it fails with:

Message action error: [Code 403] convoai.rest.forbidden - Failed to invoke action. for actionKey: confluence-page-copy

You have conveniently provided a "Debug response" page for these failures and the information in that page shows the the following as imput to the copy page action:

{  "sourceId": "2540241223",  "destinationType": "parent_page",  "destinationValue": "2434367500",  "pageTitle": "Core-Platform.Developer-Platform-ADR-2025-12-03-AI-Gateway-Third-Party-Tool-Selection" }

I have confirmed that I can perform this copy (actually "Duplicate" in the UI) with this source ID and destination, so my user does appear to have the necessary permissions. 

Any idea what might be going wrong here?

 

2 answers

0 votes
Dr Valeri Colon _Connect Centric_
Community Champion
December 14, 2025

@Matthew Welch A 403 on confluence-page-copy usually means the action is running with a different effective permission set than the UI. Even if you can duplicate the page manually, the destination parent page (or one of its ancestors) may have view/edit restrictions that block the app identity Rovo uses. Check that the destination space allows “Add pages,” the parent page has no restrictions, and the title isn’t colliding with an existing child page. A quick test is copying to a completely open parent page with a unique title—if that works, the issue is destination permissions, not the source.

Since @Rebekka Heilmann _viadee_ we have this cool banner on this post!

Screenshot 2025-12-14 124320.png

0 votes
Rebekka Heilmann (viadee)
Community Champion
December 7, 2025

Hi @Matthew Welch - welcome to the Community,

I've escalated this issue to the Atlassian Team, as it sounds like a bug to me. Have you opened a support request for this? 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events