While developing a Forge app, Rovo Studio stops responding

Question

I built a Forge app with Rovo Studio.

It worked initially, but when I came back a few days later to make improvements, the app stopped responding entirely.

A few days later I came back to make improvements, but before I changed anything the app had already stopped responding entirely — the agent just returns no response. This wasn't triggered by any adjustment I made; it went silent on its own between sessions.

Creating a brand-new app still works without issues.

Has anyone run into a similar problem?

Dr Valeri Colon (Connect Centric) · Answer

@OHNISHI Katsuya_Ricksoft_ welcome to the community. Since a new Studio app still works, I’d focus on the affected app rather than your browser. Check the Forge logs/deployment status for that app and compare them with a working one. If the agent returns literally no response and nothing changed on your side, capture the app ID, environment, timestamps, and request/debug IDs and send those to Atlassian Support. That gives them something traceable instead of treating it as a prompt issue.

Tomislav Tobijas · Answer

Oh interesting 👀

Have you tried reaching out to Atlassian Support about this? I did ask my colleague what he experienced before, and he said that, actually, the Rovo prompt part would break. Meaning, it would throw errors while he was trying to ask it to make some changes.

It would throw an error once or twice, and then it would start working again after some time. The thing is, it never actually 'replied with nothing,' so yeah... what you're seeing is a bit different.

Maaaybe try using a different browser or incognito mode, but I'm not sure if it will help 🤷

OHNISHI Katsuya_Ricksoft_ · Answer

Hi @Tomislav Tobijas ,

thanks for the thoughts! It's a different symptom than what your colleague ran into. The app doesn't break and get fixed by re-prompting — Rovo simply stops responding. The agent returns no response, and prompting again just gives the same silence.