This appears to be a GitHub integration/webhook synchronization issue rather than a runtime or deployment failure, since the existing deployment remains healthy while new GitHub pushes are no longer triggering deployments after the outage recovery.

Most likely causes are a stale/disconnected webhook, paused auto-deploy processing, or delayed webhook queue recovery on Railway’s side, so reconnecting the GitHub repo integration or re-enabling automatic deploys for project filevault may be required.

Please confirm autodeploy is enabled in your service settings and check for any skipped deployments. If it's already enabled, try disconnecting and reconnecting the GitHub repository in that same settings page, and verify the Railway GitHub App still has access to your repo at github.com/settings/installations. You can deploy your latest commit immediately via the Command Palette (Cmd/Ctrl + K) as a workaround.

the same problem Pushes to main are not consistently triggering new Railway deployments. What happened:

Commits were pushed successfully to GitHub:

822f576 Feed: add upcoming pairs API contract

9359876 Feed: generate upcoming market pairs

Railway did not automatically start deployments for these commits.

I used Railway UI Command Palette → “Deploy latest commit”, and that worked manually.

I reconnected the repository/branch, and one deploy was triggered manually/after reconnect.

Then I pushed another real tracked commit:

Chore: remove Railway autodeploy smoke file

but Railway still did not automatically trigger a deployment.

I do not want to manually use “Deploy latest commit” or reconnect the repository after every push.

Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.

It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.

You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY

If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c

Feel free to respond if your question has not been addressed.

Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.

It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.

You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY

If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c

Feel free to respond if your question has not been addressed.

Hey there,

This one's tied to the GCP outage we had on May 20 (roughly 02:25 to 07:57 UTC). GitHub webhooks sent during that window weren't received on our side, and GitHub doesn't retry them, so any pushes made during the incident never triggered deploys.

Easy fix: push any new commit and autodeploys will resume. An empty commit works too:

git commit --allow-empty -m "redeploy"
git push

Or just hit Redeploy in the dashboard.

If you push fresh and it still doesn't trigger, reply with your project ID and service ID and I'll dig in.

Sorry for the inconvenience,

Angelo