While developing a Forge app, Rovo Studio stops responding

[OHNISHI Katsuya_Ricksoft_]

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?

[Tomislav Tobijas]

Hi @OHNISHI Katsuya_Ricksoft_ ,

Would you say it stopped working after you made adjustments (guessing by prompting Rovo to make those)? I've got a colleague who's really into using Studio and trying features and apps. 
I think I did hear him saying that in some cases, Rovo could actually break the app after you asked it to make adjustments, but he would just prompt it once or twice again and it would fix it. 👀

Cheers,
Tobi

[OHNISHI Katsuya_Ricksoft_]

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.

[Tomislav Tobijas]

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 🤷