All calls against Rovo from Jira automation suddenly fail

TL;DR
Calling agent from Jira automation is now failing 100% due to the agent timing out. Anyone else seeing the same thing?

Full
I have been testing some automation rules that trigger an agent to do some work on Jira issues.

Today it suddenly isn’t working anymore. The automation calls the agent, but then never gets any response, so it eventually aborts due to taking too long.

So then I started testing a bit, and it seems it fails 100% of the time whenever an automation calls any agent. Any automation calling Rovo ends up aborted and the audit log ends with the agent call (no additional info provided, presumably because it never got a response).

Anyone seen this before or is facing the same issue?

This happens regardless of trivial the actual agent call is.

Welcome to the Atlassian developer community @erikhonn,

I just installed a Forge-based Agent and wired it into Automation. It ran fine for me.

And we haven’t published any “known incidents”: https://rovo.status.atlassian.com/

Because that requires somebody who can look into the logs, I recommend opening a support case: Rovo support | Rovo | Atlassian Support