Since this morning (Oct 5, 2026), all apps on my Community Cloud account
fail to start. They had gone to sleep after a few days of inactivity.
When I reboot, the logs stop at the same point and never reach
“Cloning repository”:
Hey there, thanks for sharing your question and all those details (and the fun emoji captions)! Sorry you’re running into this—when all your Streamlit Community Cloud apps get stuck at “Spinning up manager process…” or “Loading ‘Under construction’ GIF…” and never reach “Cloning repository,” even for a minimal hello-world app, this usually points to a backend or orchestration issue on Streamlit’s side, not a problem with your code, repo, or GitHub integration. Multiple users have reported similar symptoms, and the Streamlit team has acknowledged that sometimes the root cause is a platform-level bug or resource allocation problem that only they can resolve. See examples and troubleshooting in the docs and forum: App stuck at spinning up manager process, App deployment stuck after processed dependencies, and Community Cloud app fails at clone stage for public repo.
You’ve already tried all the recommended steps (reboot, redeploy, check deploy key, browser, etc.), so at this point, it’s best to monitor Streamlit status and consider submitting a support case if the issue persists. If you haven’t already, try deploying a minimal app (e.g., just st.write(“hello”)) in the same repo to rule out code issues, but if the logs still hang at “Spinning up manager process…”, it’s almost certainly a backend issue. Community members, feel free to jump in if you’ve seen a recent workaround! And if you have a minimum reproducible example, please share it—debugging together is what makes this community awesome.
Disconnecting…
Provisioning machine…
Preparing system…
Spinning up manager process…
Inflating balloons…
Unpacking Comic Sans RAR files…
Loading “Under construction” GIF…