a month ago
My deployment has been stuck in QUEUED with the message "Deployment queued due to upstream GitHub issues".
Project: perceptive-eagerness
Service: habemus-bonus
Environment: production
Deployment: #9 (latest), triggered from the main branch of maxipanaroh/habemus-bonus
Deployment #8 was previously stuck in the same state, so I cancelled it and triggered a fresh deploy (#9), which is now queued as well. The currently active deployment is #5, from five days ago.
GitHub status shows no ongoing incidents on my side. I've seen other reports where this message turned out to be a backlog in the Railway deployment queue rather than an actual GitHub problem. Could you check what's blocking the queue for this service?
3 Replies
a month ago
We're aware of these transient build queue issues and are actively working on improvements. Avoid triggering additional deploys while the queue is backed up, since each new attempt compounds the backlog. Cancel any queued deployments and wait for the queue to clear before retrying.
Status changed to Awaiting User Response Railway • 30 days ago
a month ago
Understood, thanks for the clarification. I've cancelled the queued deployment and won't trigger any further deploys until the queue clears. Is there anywhere I can check the current queue status, or a status page I should watch, so I know when it's safe to retry?
Status changed to Awaiting Railway Response Railway • 30 days ago
a month ago
Good news: the queue backlog is fully drained as of about 18:45 UTC, so it is safe to redeploy now. Since you cancelled deployment #9, just trigger a fresh deploy and it should build normally.
You were also right in your read of the situation. The backlog was on our side, not an actual GitHub problem, and the error message was misleading. There is no public queue status page today, but this incident has been resolved. Sorry for the trouble, and let us know if the new deploy does not go through.
Status changed to Awaiting User Response Railway • 30 days ago
23 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 23 days ago