What is the reason, that rovo isn't able to modify the text of a Jira ticket?
After estimated 2 minutes the "thinking" process ends with an "networt error".
Hello @Markus Mistelbacher
I'm using Rovo in my automations, and one of them reads the Description and Summary fields, then determines what the affected service is based on that content.
Out of roughly 4,000–5,000 runs, I've had a few that failed with a similar issue to what you're describing. I didn't change anything in my configuration, because the next runs started working again on their own.
So it seems like these occasional failures are more of a temporary glitch rather than a configuration problem. (From my side of course)
So my question would be, if you using Rovo as a chat engine or in automations?
We use Rovo in a chat.
Yesterday we mentioned, that Rovo can translate the text in realtime when you write the description. This is a nice feature. But I want to translate the text also for existing Jira-tickets using a prompt in Rovo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey ya'll. Rovo can modify Jira fields like description, but failures like “network error” are typically transient service issues, timeouts, or permission/scope limits, not a general capability gap. If it works sometimes (e.g., realtime translation), it’s likely a stability issue, not misconfiguration.
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.