Rovo Agent can no longer read Loom transcripts after LLM update

[YAMASHITA Akiko_Ricksoft_]

We are developing a Rovo agent that analyses the content of recorded sales meetings. Since we record our meetings using Loom, we decided to provide the Loom recording URL as an instruction and have the agent analyse the transcript.

Around 25 March 2026, we were able to retrieve transcripts using a skill called "Content read" (?), but when we tried again after 2 April, the Loom transcripts could no longer be read.

This timing coincides with when the LLM for Rovo agents was updated. Was there a specification change, or is this a bug?

[Arkadiusz Wroblewski · Accepted solution]

Hello and welcome to Community @YAMASHITA Akiko_Ricksoft_ 

This looks like a regression from Atlassian’s recent Rovo Agent LLM upgrade, which has been known to disrupt third-party transcript extraction.

Test the Loom URL inside a brand-new test agent. If that fails too, raise a ticket with Atlassian Support and include your agent link. In the meantime, the most reliable workaround is to copy the transcript text onto a Confluence page and point your agent there, as native data paths remain completely stable.

Best, 

Arkadiusz 🤠

[YAMASHITA Akiko_Ricksoft_]

Hi Arkadiusz,

Thank you very much for your quick and helpful response, and for the warm welcome to the Community. Your explanation about the recent Rovo Agent LLM upgrade causing transcript extraction issues is very useful context.

I tested the Loom URL with a brand-new test agent as you recommended, and the same issue reproduces there. Given that, I'll raise a ticket with Atlassian Support and include the agent link. I'll also try the Confluence page workaround you suggested in the meantime.

Thanks again for your help!

Best,
Akiko