App URL:
Repository:
svintit/band-scheduler
Branch:
main
Entry point:
app/web.py
Deployment started:
2026-08-05 16:39 UTC
The logs stop at:
Provisioning machine…
Preparing system…
Spinning up manager process…
The repository deploy key exists, is verified, and is read-only.
viewerAuthEnabled is false.
Rebooting, recreating the app, and using another browser do not help.
Other Streamlit apps work.
The app never reaches repository cloning or dependency installation.
Hey there, thanks for sharing your question and all those details! 
When your Streamlit Community Cloud app gets stuck at “Spinning up manager process…” and never reaches the repository cloning or dependency installation steps—even after rebooting, recreating, and confirming the deploy key—this usually points to a backend or orchestration issue on Streamlit’s side, not a problem with your repo or config. Multiple users have reported similar symptoms where the logs stop at this stage, 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 and App deployment stuck after processed dependencies.
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!
Sources: