Important Update -- Rovo Agents are getting a new backend LLM model

[Neha Asthana]

I still see an issue with my old agent, whereas it is not a problem for new agents created. Please help. Where should I raise the ticket? @Jensen Fleming 

[Jensen Fleming]

@Stefan Kirchner -- Just a quick update, to diagnose this issue, we will need to know more details on the tools used. We don't believe it's a model issue, other models have a similar limit, so we need to look at the logs. If you can send me a ticket link you create with support, that would be great. Thank you so much. 

[Jensen Fleming]

@neha -- Interesting. Is the new agent you created on the new model? All new agents are on the new model by default. 

> You can raise a ticket with support here:  https://support.atlassian.com/contact/#/

[Jensen Fleming]

FYI Details on the extending testing window here: https://community.atlassian.com/forums/Atlassian-AI-Rovo-articles/Extended-Testing-Window-for-New-Rovo-Agents-Backend-Model-Until/ba-p/3214209#M2071

This will be reflected in the UI shortly. 

[Stefan Kirchner]

Hello @Jensen Fleming: You will receive it from our internal company Atlassian team. 

Ticket: https://support.atlassian.com/requests/CES-150553

[Neha Asthana]

 @Jensen Fleming I tried raising a ticket but no luck - Can you help me raise a ticket on my behalf to speed up the resolution? 

[Jordan Stewart]

Hello @Jensen Fleming facing similar issues with our custom rovo agents receiving this error, please advise on how this can resolved: 

[tom_hawkins]

Thanks for this info @Jensen Fleming  , today a popup message in Studio told me about "Exciting changes have come to agents" including "Subagents to replace scenarios" I'm assuming that that isn't part of the abovementioned LLM change given "Nothing visible. It’s a backend change only. We’re upgrading the underlying model behind the scenes." above BUT I haven't been able to find an equivalent info page about that change apart from the popups I was shown, is there one please? (For example I'd like to know whether migrating just one multiscenario agent to test in the new subagent model whilst leaving the others working as is for the moment is supported please)