a month ago
Subject: Deployment stuck in "Queued" state for hours — project erp-api (beneficial-surprise)
Hi Railway team,
My deployments have been stuck in "Queued" status for several hours and never start building, even after multiple retries.
Details:
- Project: beneficial-surprise
- Service: erp-api
- Project ID: 54f7c76a-2f0d-4469-9cd4-81d2cbb7b391
- Service ID: c6a93f44-bf38-4f83-80a8-ec2c98245f96
- Environment ID: d9f2d154-37e9-46fc-9ab7-26979e92a4a4
- Production URL: erp-api-production-4667.up.railway.app
What's happening:
- Every new deployment from a GitHub push immediately shows status "QUEUED" with the message "Deployment queued due to upstream GitHub issues."
- There are no build logs at all — the deployment never starts.
- The currently active deployment (7-8 hours old) is still running fine, so the service itself is online, but no new code changes can be deployed.
- I checked both GitHub Status (githubstatus.com) and Railway Status (status.railway.com) — both show all systems operational, so this doesn't appear to be a general outage.
What I've already tried (none of it worked):
- Pushed multiple new commits (including empty commits) to trigger fresh deployments — each one goes straight to "Queued" and stays there.
- Removed the stuck "Queued" deployments and retried — same result immediately.
- Verified the GitHub repo connection and "Auto deploys when pushed to GitHub" are correctly configured in Settings.
- Used the "Latest deploy" action from the service context menu — it only opens the existing active deployment, doesn't trigger a new build.
- I had a second, unrelated Railway project ("fantastic-imagination") also connected to the same GitHub repo and experiencing the identical stuck-queue symptom. I deleted that service entirely, but the issue in "beneficial-surprise" persisted.
Account context: I'm currently on the Trial plan with $4.21 in credits remaining. I don't know if this is related to the queue getting stuck, but wanted to flag it in case it is.
Recent commit hashes that got stuck in the queue: acd3f7a, cf0720b.
Could you please investigate why deployments aren't leaving the queue, and help me get a build running again?
Thanks,
Matias
3 Replies
a month ago
Your workspace is currently in an INACTIVE state, which is why new deployments are being queued rather than building. The "upstream GitHub issues" message is misleading - the queue is caused by the workspace's inactive subscription state, not a GitHub problem. Your credit balance is still intact ($5.00), so this does not appear to be credit exhaustion. Please try logging out and back in, then check whether your workspace shows as active at railway.com/workspace/billing. If the issue persists after that, reply here so we can take a closer look.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Hi, I'm still having the same problem. It was fixed yesterday, but it happened again today at almost the same time. I've already logged out and back in, and I've also checked if my user account is active.
How can I fix this?
Thanks
Status changed to Awaiting Railway Response Railway • 30 days ago
a month ago
Sorry for the repeat, and thanks for the thorough report. You hit the same problem twice: our deploy queue for trial and free workspaces backed up yesterday and again today. Despite the message, it was not a GitHub problem, and the earlier reply blaming your workspace state was also wrong. Your account and credits are fine.
The backlog is now fully cleared, and your latest deployment built and went live at 18:49 UTC today, so erp-api is running your newest code. New pushes should deploy normally. If it happens a third time, reply here and we will take it up directly.
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