a month ago
Hi Railway Support Team,
I am opening this ticket because my project is not triggering new deployments after pushing to GitHub.
Yesterday, during/after the platform issues, I pushed an important update to my repository (updating to ex8.1). The code is already live on GitHub, but Railway completely missed the webhook and didn't trigger the build.
I have already tried pushing an empty commit to force it, and also tried triggering a manual redeploy from the dashboard, but the service seems "stuck" and is not reacting to my repository updates.
Could you please force a sync or check if the webhooks for my project are stuck on your end?
Thank you for your help!
5 Replies
a month ago
We experienced a major service disruption that has since been resolved, and GitHub webhooks pushed during the outage window were missed. Your existing deployment is still running healthy, but no new build was triggered. Now that the incident is resolved, pushing a new commit or clicking "Deploy" from the service's dashboard should trigger the build normally. If it still does not pick up the commit, try disconnecting and reconnecting your GitHub repo in the service settings.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
We experienced a [major service disruption](https://status.railway.com/incident/I23M92U0) that has since been resolved, and GitHub webhooks pushed during the outage window were missed. Your existing deployment is still running healthy, but no new build was triggered. Now that the incident is resolved, pushing a new commit or clicking "Deploy" from the service's dashboard should trigger the build normally. If it still does not pick up the commit, try disconnecting and reconnecting your GitHub repo in the service settings.
a month ago
I already tried disconnecting and reconnecting the GitHub repository as suggested, but it didn't work. The deployment is still stuck.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This is a lingering effect of the service disruption on May 19 - your existing deployment is still running fine, but the webhook pipeline for new commits got stuck. Please try opening the Command Palette (CMD/Ctrl + K) on your service page and selecting "Deploy Latest Commit" - this uses a different trigger path than the dashboard redeploy button. If that still doesn't work, try removing the current service, re-adding it from your GitHub repo, and it should pick up the latest commit on creation.
Note that we are still working through a large backlog of deployments which means it make take some time to redeploy. (At the moment, Hobby deployments are paused while we try to catch up.) https://status.railway.com/incident/KVZ1Z8GY
So sorry for this problem!
Status changed to Awaiting User Response Railway • about 1 month ago
sam-a
This is a lingering effect of the [service disruption on May 19](https://status.railway.com/incident/I23M92U0) - your existing deployment is still running fine, but the webhook pipeline for new commits got stuck. Please try opening the Command Palette (CMD/Ctrl + K) on your service page and selecting "Deploy Latest Commit" - this uses a different trigger path than the dashboard redeploy button. If that still doesn't work, try removing the current service, re-adding it from your GitHub repo, and it should pick up the latest commit on creation. Note that we are still working through a large backlog of deployments which means it make take some time to redeploy. (At the moment, Hobby deployments are paused while we try to catch up.) https://status.railway.com/incident/KVZ1Z8GY So sorry for this problem!
a month ago
Thanks for the reply, Sam.
I understand that Hobby deployments are currently paused due to the backlog from the May 19 disruption. However, as I mentioned before, I am completely on a mobile Android device. I physically cannot open the Command Palette (CMD/Ctrl + K) since I don't have a desktop keyboard, and the mobile browser interface does not provide an alternative shortcut to bypass this.
Since I am trapped between a paused Hobby queue and a mobile interface that prevents me from using the Command Palette workaround, I am completely stuck.
Could your team please manually trigger the "Deploy Latest Commit" from your backend for my ArenaX service, or manually bypass the pause for this specific deployment? I really need version 8.1 to go live.
Thank you!
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hey, I just took a look and all of your services seem to be up and healthy.
I'm gonna close this thread, but please respond here again with links to the relevant projects so we can take a deeper look if there are still ongoing issues.
Sorry you were affected by this, thanks for hanging in there with us.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved mykal • about 1 month ago