an hour ago
Deployment stuck on "Waiting for deployment slot" for over an hour Build always completes successfully (image builds and pushes without errors). After that, the deployment gets stuck on "Waiting for deployment slot" indefinitely. What I've already tried: Tried different regions (EU West, Southeast Asia) — same result in both Stopped all other services on my account to rule out a vCPU/resource limit — did not help A completely unrelated project on the same account (different repo, different tech stack) gets stuck the exact same way This looks like an account-level or platform-side issue rather than something related to my specific project. Deployment ID: [dd0b0575-0220-4a90-bad6-e189eb09b7fc]
4 Replies
an hour ago
Your deployment is queued behind an earlier deployment of the same bot in your other project. That earlier deployment started at 18:53 UTC and has been stuck in its pre-deploy command step for about two and a half hours. It is still holding a deploy slot, and six more deployments of that service are queued behind it.
It started while we had an incident causing slow or stuck deployments, and Hobby deployments were paused for part of it. The incident was resolved at 19:15 UTC, and you can see the full timeline here.
Its logs show nothing after the container started, so the pre-deploy command never exited. Cancel that stuck deployment, plus the extra queued redeploys of it, from that service's deployments list. The backlog then drains on its own and this deployment can start.
Status changed to Awaiting User Response Railway • about 1 hour ago
Railway
Your deployment is queued behind an earlier deployment of the same bot in your other project. That earlier deployment started at 18:53 UTC and has been stuck in its pre-deploy command step for about two and a half hours. It is still holding a deploy slot, and six more deployments of that service are queued behind it. It started while we had an incident causing slow or stuck deployments, and Hobby deployments were paused for part of it. The incident was resolved at 19:15 UTC, and you can see the full timeline [here](https://status.railway.com/incident/YYTG8I10). Its logs show nothing after the container started, so the pre-deploy command never exited. Cancel that stuck deployment, plus the extra queued redeploys of it, from that service's deployments list. The backlog then drains on its own and this deployment can start.
37 minutes ago
Do not work
Status changed to Awaiting Railway Response Railway • 37 minutes ago
35 minutes ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 35 minutes ago
31 minutes ago
Sanity check, aborting/cancelling all queued and active deployments, then redeploying did not fix it?
0x5b62656e5d
Sanity check, aborting/cancelling all queued and active deployments, then redeploying did not fix it?
23 minutes ago
The same issue is occurring across multiple services/projects. They all get through the build successfully and then appear to stall around the image push/deployment stage.