Extended Testing Window for New Rovo Agents Backend Model Until April 14

[#1]

We’re sharing an important update on the rollout of the new backend LLM model that powers Rovo agents.

In our original announcement, we said all remaining agents would move to the new model by March 31. However, based on your feedback, we’re adjusting that plan.

What’s changed

1. You asked for more time to test – we’re giving it.
   Many of you told us you need a bit more runway to validate critical agents, especially complex automations. We’ve heard you, and we’re extending the testing period for 2 more weeks.

2. Early results look good.
   So far, around 30% of existing agents traffic is using the new model. Across those agents, we’re seeing a large reduction in errors compared to the previous model, and better stability overall.

3. Extended testing window (all customers).
   We’re extending the testing window for the new model to April 14 (US date). Until then, you’ll keep the ability to choose which model your agents run on.

How this works

• Existing agents will continue to default to the old model for now.
  We won’t force‑flip your existing agents yet.

• You have an opt‑in option to move agents to the new model.
  In Studio, you can switch an individual agent to the new model, run your tests and evaluations, and switch back if needed during the testing window.

• On April 14 (US date), all remaining agents will be moved to the new model and the opt‑in/opt‑out toggle will be removed.

Recommended way to test

If you haven’t tested the new model yet, we strongly recommend you:

Duplicate (recommended for high‑value agents)

1. From Studio, select Agents

2. Using the more actions (…) menu, select Duplicate

3. The duplicated version of the agent will automatically use the updated model without affecting the original agent.

4. Run your key prompts and evaluations.

Use the model toggle

1. From Studio, select Agents

2. Select the agent you’d like to test or migrate

3. You should be taken to the agent’s Overview page

4. Look for Swap to new model

5. Toggle it ON

6. Run your key prompts and evaluations and decide whether to keep it on the new model, or swap it back while you iterate.

If something looks off – please contact our our support team

If you notice regressions or unexpected behavior when running on the new model, it’s strongly preferred that you open a support ticket rather than only sharing feedback in this blog.

Support tickets let us:

• Access the relevant logs and telemetry for your agent

• Track issues systematically across customers

• Prioritize and fix problems faster.

When you open a ticket, please include:

• A link to the affected agent

• A short description of what changed (e.g. “automations failing”, “unexpected replies vs old model”)

• One or more example prompts where you see the problem

• Debug logs from your conversation (click the { } button under the agent’s response)

---

We’ll continue to monitor migration rates, opt‑in/opt‑out behavior, and support volume closely through April 14, and we’ll update this page again if anything changes.

[Amish Khatri]

What is the impact on all out-of-box agents? Are their LLMs also being changed? How can they be duplicated?

[Jensen Fleming]

@Amish Khatri  Great question! They're LLM will be changed, we are considering flipping theirs before the April 14th deadline, but for now, you can duplicate an OOTB agent in the same way you can any other agent. Navigate to it -> `...` and click Duplicate. 

[Raghavendran_Narayanan]

@Jensen Fleming  - Need help. Would you be publishing the known error reported so far with this new model and steps to remediate.  Additionally any best practices you can share to get the most out of the new models , like updating the design, instructions etc , that would be much appreciated! .

[Julian Hermes]

Hey Jensen, I'm not sure, but there might be an issue with using Rovo-Agents with the new model via automations. Even when I duplicated our Agent and switched it in our automation it is not working since today. We did not change the automation and it worked well till today.

[Prasath Venkatappan Badri]

Hi Jensen,

Our Jira Automation rules are failing with an "Aborted" status specifically when the Rovo Agent component is used.

Looking for any advice or confirmation if this is a widespread issue.

Thanks,
Badri Prasath V

[Nahed Hamdi]

Hi Jensen,

We’re currently facing the same issue with Jira Automation, where rules involving Rovo agents are getting aborted.

Could you please advise if there are any known limitations or recommended patterns to handle this?

Thanks,

[Barbara Szczesniak]

@Julian Hermes @Prasath Venkatappan Badri @Nahed Hamdi In case you are not aware, a new incident is reported on the Jira Status page in relation to this issue. 

[Fabrizio Magistrelli]

We are also getting aborted automations using ROVO

[Zita Bagi]

"If something looks off – please contact our our support team"

Using "our our" instead of "our" looks off.