Deploys not triggering after May 20 outage
yakubacademy
HOBBYOP

a month ago

Hi Railway team,

After the outage on May 20 (02:25–07:57 UTC), my auto-deploys stopped working. I have pushed several commits since then but none of them triggered a deployment.

Project: daring-benevolence

Service: worker

Latest commit: 29d8236

Could you please manually trigger a deployment of the latest commit or re-sync the GitHub webhook?

Thank you!

Solved

3 Replies

Railway
BOT

a month ago

Your worker service's last successful deployment was on 2026-05-20 at 16:27 UTC, and the auto-deploy issue you're experiencing is related to the ongoing recovery from the major platform incident that began on May 19. We are actively working to restore all affected functionality, including GitHub webhook integrations. In the meantime, you can manually trigger a deployment from the Command Palette (CMD/Ctrl + K) by selecting "Deploy Latest Commit."


Status changed to Awaiting User Response Railway about 1 month ago


yakubacademy
HOBBYOP

a month ago

I tried CMD+K → "Deploy Latest Commit" but it shows "Failed to trigger deployment — Deploys have been paused temporarily". The manual trigger also doesn't work. Please unpause deploys for my account manually.


Status changed to Awaiting Railway Response Railway about 1 month ago


Railway
BOT

a month ago

Your worker service has a new successful deployment as of 19:19 UTC today, which is after you reported the issue. The deploy pause related to the platform recovery has been lifted for your service. If future commits still do not trigger auto-deploys, please let us know and we will investigate further.


Status changed to Awaiting User Response Railway about 1 month ago


Status changed to Solved Railway about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...