I’m running my app locally and I deployed it. When running the app, the page shows app error, so I thought my code went wrong. After debugging I just change directly back to a version history that originally worked, and reboot the app. However when reopen the app, it’s forever in the oven. I don’t know what might be wrong.
Hey there, thanks for sharing your question and your repo link! You’re not alone—many folks have run into the “forever in the oven” issue on Streamlit Community Cloud, even after reverting to a previously working version. This usually points to deployment or configuration issues, not necessarily your code.
Here’s what you should try, based on official docs and community experience:
Reboot the App: From your workspace or Cloud logs, use the “Reboot” option to force a fresh build. This often resolves temporary deployment glitches (official reboot instructions).
Check Python Version: Streamlit now requires Python ≥3.10. If your app is pinned to an older version (like 3.9), update it in your app settings and reboot (community report).
Review requirements.txt: Make sure all dependencies are listed, with no typos or OS-specific packages. Only include packages not in the Python standard library (deployment troubleshooting).
Resource Limits: If your app is resource-intensive, it may exceed Community Cloud limits (2.7GB RAM, 2 CPU cores). Try simplifying the app or using caching (st.cache_data) to reduce memory usage (resource limits guide).
Delete and Redeploy: If all else fails, delete the app and redeploy from scratch. This has resolved persistent “in the oven” issues for many users (community example).
If you’re still stuck, please share a minimum reproducible example and your requirements.txt so the community can help debug further! Community members, feel free to jump in with your insights or similar experiences.