I’m running into a strange issue with a Confluence automation that uses a Rovo Agent, and I’m curious whether anyone else has seen the same behavior.
I built an automation rule that works like this:
seo-check)This setup used to work for me.
Since switching the agent to the new model, the automation no longer completes properly. In the audit log, the runs stay stuck on WAITING under In Progress and never finish.
What I already checked:
{{agentResponse}} is correctly used in the comment stepWAITINGWhat’s even stranger is that switching back to the old model did not seem to fix it either.
So now I’m wondering:
WAITING?Would really appreciate any experiences or ideas.
@Patricia Modispacher _K15t_ @Tomislav Tobijas
I still believe it will take quite some time before agents behave in a truly predictable and reliable way. That is probably my biggest concern at the moment. The core issue is not only capability, but consistency: the results are still not stable enough from one case to another, which makes it difficult to fully trust them in more critical or repeatable Scenarios.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Patricia Modispacher _K15t_ ,
I've actually experienced the opposite right now.
We have an agent within automation that posts weekly highlights in the Teams channel and up until today, everything worked perfectly (on old model). I've re-run the old agent twice today, and it said it didn't find any highlights, but when I switched the model (to the new one), it published everything successfully. 👀
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.