The Rovo Agent’s ImageReadTool returns an HTTP 404 (Not Found) erro

[Anna Ziętek]

The Rovo Agent’s ImageReadTool returns an HTTP 404 (Not Found) error when attempting to access images embedded on a Confluence page. What could be causing this issue?

The image attachments have been uploaded directly to the Confluence page and are visible to users. They are not linked from any external source and were re-uploaded to ensure that they are stored as native Confluence attachments.

The Rovo Agent correctly detects the images and identifies their number on the page. However, ImageReadTool fails when attempting to read their content and returns an HTTP 404 (Not Found) error.

The agent is able to process the same images successfully only when the image files are attached directly to the agent’s chat and the relevant Confluence page is provided as a source. When the agent attempts to access the images directly from the Confluence page using ImageReadTool, the 404 error occurs.

[Germán Morales · Accepted solution]

Hi @Anna Ziętek ,

This matches a known Rovo limitation rather than a missing or incorrectly uploaded Confluence attachment. Atlassian tracks it under ROVO-388: Rovo can process images uploaded directly into Chat, but it cannot currently process images embedded in Confluence pages or attached to Jira work items.

That explains why the agent can detect the image references on the page but ImageReadTool cannot read their contents. Re-uploading the files to the page or changing their format will not bypass the limitation.

For now, upload the images directly to the Rovo conversation, or add the relevant information from each image as normal text on the Confluence page. You can vote for and watch ROVO-388 for updates. If Atlassian needs diagnostics, use the { } option below the agent response to copy the request and agent IDs, as described in the Rovo debug response guide.

[Rebekka Heilmann _viadee_]

Rovo-388 is not quite up to date. Reading Images from Jira works

[Dr Valeri Colon _Connect Centric_]

@Anna Ziętek welcome to the community. Your testing strongly suggests this isn’t an attachment-upload problem. ROVO-388 currently documents a limitation with Rovo reading images embedded in Confluence content, which matches what you’re seeing: the agent recognizes the image reference but can’t retrieve the image itself.

One update: reports indicate Jira image reading now works, so ROVO-388 appears partly outdated. For Confluence, I’d watch ROVO-388 and raise a Support ticket with the 404 plus Rovo request/agent IDs so Atlassian can confirm whether your case is the known limitation or a newer defect.