a month ago
d
3 Replies
Status changed to Awaiting Railway Response Railway • 30 days ago
a month ago
There are ongoing intermittent upstream GitHub issues right now affecting deployments. In the mean time you could try using railway up since that doesn't depend on GitHub, otherwise you could try waiting a bit before trying again
Railway
All deployments on your account are currently showing as completed successfully, so the "queued due to upstream GitHub issues" state has cleared. If a new deployment gets stuck in the queue, canceling it and triggering a fresh deploy from the dashboard will resolve it.
a month ago
Hi Railway team,
Two of my deployments have been stuck in Queued status for a while now, both showing the message:
"Deployment queued due to upstream GitHub issues"
Commit: "Update README.md" — triggered ~[X] minutes/hours ago via GitHub
Commit: "new changes" — triggered shortly after
Both GitHub Status and Railway Status currently show all systems operational, so this doesn't appear to be a public incident.
What I've already tried:
Retried/re-pushed a commit — still queued
Waited to see if it clears on its own — no change
Could you please help me clear this queue, or let me know if there's a webhook/GitHub App connection issue on my project that needs to be reset? Happy to provide the project ID / service name / deployment IDs if needed.
Project: X0Tech-Animated
Thanks for the help!
Status changed to Awaiting Railway Response Railway • 30 days ago
Status changed to Awaiting User Response Railway • 30 days ago
a month ago
This is resolved. The queue backlog was on our side rather than GitHub's, and it has now been cleared.
Your latest deployment built and went live at 18:55 UTC today. New deploys should go through normally. Sorry for the disruption, and let us know here if anything gets stuck again.
Status changed to Solved Railway • 30 days ago