Cloud test app is not automatically redeploying when I push changes to GitHub

Deployment
1

Title: Streamlit Community Cloud not automatically redeploying after GitHub push

Hello Streamlit Support,

My Streamlit Community Cloud test app is not automatically redeploying when I push changes to GitHub.

App: cognexa-ai-test
Repository: SrikanthBhimani/ai-chatbot
Branch: feature/chat-history
Main file: app.py
Latest commit: 2560ff890a0739dd7eab0d7c309780ed04a686dd — Add optional web search

I have verified that:

  • The push to the correct GitHub branch succeeded.

  • The GitHub webhook payload contains the correct branch and latest commit.

  • The repository webhook points to https://share.streamlit.io/hook.

  • The webhook delivery shows a response from the endpoint.

  • The app’s Cloud logs still show the earlier startup at 09:20 UTC, with no new deployment corresponding to the latest push.

I need automatic deployments to work reliably without manually rebooting the app after every push.

Could you help identify why the GitHub push is not triggering a new deployment? I want to preserve the existing app and avoid deleting or recreating it.

Thank you.

2

Hey there, thanks for the detailed info and for being so thorough with your troubleshooting! :waving_hand: This issue—where Streamlit Community Cloud doesn’t automatically redeploy after a GitHub push, even though webhooks and commits look correct—has been reported by several users. Normally, changes pushed to the connected branch should trigger an immediate update, but sometimes sync issues or backend hiccups prevent this, requiring a manual reboot for updates to appear. This is not the intended behavior, and it’s not something you can fix from your end if all your GitHub integration settings are correct.

Recommended steps from both the official docs and community reports are: (1) disconnect and reconnect your GitHub account in Streamlit Community Cloud to refresh permissions and sync, (2) check app logs for errors, and (3) if the issue persists, consider deleting and redeploying as a last resort (though you want to avoid this). This is a known platform-side issue, and sometimes it resolves itself after a short while or after reconnecting GitHub. If you can, please share a minimum reproducible example or your repo link so the community can help debug further. Community members, feel free to jump in with your insights!

Sources: