nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Rovo Agent Performance Over the Past Few Days

Chris Green

Has anyone else noticed slower processing with Rovo Agents over the past couple of days, particularly agents that retrieve or analyze ticket (work item) data using JQL queries?

Rovo Agents have been working well for our use cases, but this week, some of the agents I run daily have started taking significantly longer to complete and, in some cases, have timed out.

I’m hoping to keep this discussion focused on that recent change, as these same agents were completing reliably before this week.

Has anyone experienced something similar, particularly with agents querying work item data?

Accepted answers

Matthew Sinclair

There's been some "Turbulence" in Rovo this week - partial outages/etc.

I'd suggest keeping an eye on it to see if things continue trend wise into next week.

All comments

Matthew Sinclair

There's been some "Turbulence" in Rovo this week - partial outages/etc.

I'd suggest keeping an eye on it to see if things continue trend wise into next week.

Arkadiusz Wroblewski

Hello @Chris Green

Capture the usual versus current runtime, timestamps, and the request ID from Debug response where available.

Does the same JQL still return quickly when run directly in Jira? That comparison would help Atlassian Support investigate where the delay occurs.

Best,

Arek🤠

Chris Green

We are going into a week now with degraded performance with Rovo Agents. If I copy out agent instructions and post into a Rovo Chat, it works (sometimes) so appears to be something with Agents specifically. I haven't seen any updates from Atlassian.

It does appear that OpenAI has been dealing with major service disruptions this past week so wondering if this is related.

Anwesha Pan

Hi @Chris Green

Since its persistent, I would suggest you to open a ticket

Go to Atlassian Support
Under Technical Issues -> choose Atlassian Intelligence/ Rovo.
Provide your Tenant Cloud ID and specific Agent execution timestamps

Thanks,
Anwesha

Josh

For a quick isolation test, run the same agent with a narrow project/status/date filter and a small result set, then compare it with the original JQL. Expensive or unbounded searches, large attachments, and multiple sequential tool calls can make an agent look slow even when the model is healthy. I would also check the agent run history for throttling, retries, or timeouts and compare the timestamps with Atlassian Status. If the narrowed test is still slow, capture the site, agent, UTC timestamps, and a redacted run/correlation ID for Support rather than repeatedly retrying the same run.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-management

rovo