Streamlit Community Cloud not auto-deploying after successful GitHub webhook (HTTP 200)

Community Cloud
,
1

Hello Streamlit Community,

I need help diagnosing an automatic deployment issue with my Streamlit Community Cloud application.

App: https://ipex-ia.streamlit.app/

Configuration:

  • Repository: patriciacarolinasoto8-source/igp-ia-licitaciones (private)

  • Branch: feature/supabase-ipex-preparacion

  • Main file: streamlit_cloud.py

  • Python: 3.12

Problem:

My application continues running an older Git commit even though newer commits have been pushed successfully to the configured GitHub branch.

The application displays commit bb1a6a7, while GitHub contains newer commits.

What I have verified:

  1. Streamlit Community Cloud is connected to my GitHub account.

  2. The Streamlit OAuth application has access to private repositories and repository hooks.

  3. The repository webhook is active and configured for push events.

  4. GitHub successfully delivered a push event to https://share.streamlit.io/hook on October 20, 2026, at 06:58 UTC.

  5. The webhook returned HTTP 200.

  6. The delivered event targeted the correct branch and commit c5aec5f.

  7. The application’s available startup logs still show the older commit bb1a6a7, with no subsequent update visible in those logs.

Expected behavior:

The application should automatically update when new commits are pushed to its configured branch, without requiring a manual reboot through Manage app.

Questions:

  • Why might a successfully delivered webhook not result in an application update?

  • How can I verify whether Community Cloud processed the webhook and attempted to deploy the new commit?

  • Is there a way to restore automatic deployments without deleting or recreating the application?

I would appreciate guidance on troubleshooting this issue while preserving the existing app, URL, and configuration.

Thank you!

2

Thanks for the detailed diagnostics. Community Cloud normally reflects GitHub pushes in almost real time, but the available documentation doesn’t explain how to confirm whether a specific webhook was processed—so HTTP 200 alone doesn’t establish that a deployment ran. Check Manage app → Cloud logs for the attempted update and errors; those logs are the documented primary troubleshooting location. Also verify the deployed app’s repository, branch, and entrypoint match the push, since Community Cloud identifies apps by those GitHub coordinates. (Manage your app, Manage your GitHub connection)

To try restoring updates without deleting the app, revoke the “Streamlit” app’s repository access in GitHub settings, then sign back in to Community Cloud and reauthorize it; the docs describe this as a way to prompt GitHub authorization again. Confirm the private-repository access is still granted. The docs don’t guarantee this fixes missed deployments, nor describe another way to inspect webhook processing. If the logs show no new attempt despite the successful delivery, include the app’s Cloud logs and commit/branch details when asking the community for help. (Manage your GitHub connection)

Sources: