All apps stuck at "Your app is in the oven" even after account reset

Subject: All apps stuck at “Your app is in the oven” even after account reset

Hi Streamlit team,

I’m experiencing a persistent issue where any app I deploy is stuck at the “Your app is in the oven” screen indefinitely, regardless of the code I use.

Here are the details:

  • I tried deploying multiple .py files, including official Streamlit template apps → All get stuck.
  • I deleted my Streamlit Cloud account and re-registered using the same GitHub account → same result.
  • I also tried using the template app deployment directly from streamlit.io/deploy → still stuck.
  • My apps don’t produce any logs, and there are no errors shown in the UI.
  • I confirmed that my GitHub repo and app code work locally without issue.
  • The GitHub account is public, and repos are accessible.

This behavior leads me to believe that my GitHub account, or associated resources, may have been flagged or restricted internally, as no deployment succeeds regardless of content or app configuration.

Could you please investigate and let me know if my GitHub identity or account is under any restriction?

GitHub Repo: GitHub - minimin227/Dashboard_for_public_data: A streamlit app to show dashboard for public data project
Example App URL: https://chatbot-zjmop699vr.streamlit.app/

Thank you!

1 Like

I experienced the same error. All of my apps used to work as normal but suddenly everything just stopped working anymore.

me too!! everything just keep spinning !

I tried rebooting but still in the same issue

This seemed to be an issue the other night as well. My thoughts were it had something to do with the Streamlit Cloud Servers. Last time it just fixed by morning with my changes. I was still able to host and develop locally, then upload my changes, which got registered by morning.

Hi! We’ve identified one issue and applied a mitigation. Did the application load for you?

2 Likes

The apps are working now without any issues.

it works now. thanks!

I encountered the same error. Restarting the application did not resolve the issue.