a month ago
My deployments are stuck in QUEUED status and never transition to building.
Multiple deployments queued but never build. Tried canceling and redeploying multiple times with no change.
17 Replies
a month ago
Your deployment is currently in a queue due to limited access, which can occur on the Hobby plan during high traffic periods when Pro/Enterprise users are prioritized for build resources. Queued deployments will automatically process when capacity is available, and you can read more about this in our docs. Upgrading to the Pro plan bypasses this queue entirely.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Your deployment is currently in a queue due to limited access, which can occur on the Hobby plan during high traffic periods when Pro/Enterprise users are prioritized for build resources. Queued deployments will automatically process when capacity is available, and you can read more about this in [our docs](https://docs.railway.com/deployments/reference#deployments-paused---limited-access). Upgrading to the Pro plan bypasses this queue entirely.
a month ago
well I am a pro user already sitting 30 min with stuck builds. Common guys!
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hi optimability and Railway,
I'm stuck with the same issue (QUEUED) and using PRO, so some more prio to this issue maybe?
a month ago
Same problem here
Railway
Your deployment is currently in a queue due to limited access, which can occur on the Hobby plan during high traffic periods when Pro/Enterprise users are prioritized for build resources. Queued deployments will automatically process when capacity is available, and you can read more about this in [our docs](https://docs.railway.com/deployments/reference#deployments-paused---limited-access). Upgrading to the Pro plan bypasses this queue entirely.
a month ago
I have same problem, 10 delayed minutes
a month ago
MISMO PROBLEMA, CUANDO PUEDEN RESOLVER ESTE PROBLEMA
a month ago
30 delayed minutes, and still on queued status
Railway
Your deployment is currently in a queue due to limited access, which can occur on the Hobby plan during high traffic periods when Pro/Enterprise users are prioritized for build resources. Queued deployments will automatically process when capacity is available, and you can read more about this in [our docs](https://docs.railway.com/deployments/reference#deployments-paused---limited-access). Upgrading to the Pro plan bypasses this queue entirely.
a month ago
https://status.railway.com/incident/ZLI8N955 --> i'm not sure, but are you guys also fixing this issue for PRO tiers? or ? because like i mentioned earlier i've the same issues....
a month ago
I'm pro and I'm 30 min waiting atm..
a month ago
There is currently an active incident affecting build capacity, which is causing deployments to remain stuck in the queue. You can follow the progress here: https://status.railway.com/incident/ZLI8N955
We have throttled the free and hobby users, but the delays impact other users possibly.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Also been waiting 30m+
Status changed to Awaiting Railway Response Railway • about 1 month ago
pbr-2025
https://status.railway.com/incident/ZLI8N955 --> i'm not sure, but are you guys also fixing this issue for PRO tiers? or ? because like i mentioned earlier i've the same issues....
a month ago
As far as I know, Pro plans get indirectly affected by these types of incidents. Even if they're prioritised, they're still affected by the backpressure of people spamming deploys post-incident.
medim
As far as I know, Pro plans get indirectly affected by these types of incidents. Even if they're prioritised, they're still affected by the backpressure of people spamming deploys post-incident.
a month ago
Ok, thanks for the reply and starting investigation. Waiting till its fixed it the only thing i can do right now i guess.
stephenplusplus
Also been waiting 30m+
a month ago
1 hour +
medim
As far as I know, Pro plans get indirectly affected by these types of incidents. Even if they're prioritised, they're still affected by the backpressure of people spamming deploys post-incident.
a month ago
Identified
We have identified the issue and deployed a fix. Builds should be progressing now.
We will continue to monitor and provide an update once performance has fully stabilized.
Worked for one deploy, but now after redeploy, again i got stuck in QUEUED...So not fixed yet i guess?
pbr-2025
IdentifiedWe have identified the issue and deployed a fix. Builds should be progressing now.We will continue to monitor and provide an update once performance has fully stabilized.Worked for one deploy, but now after redeploy, again i got stuck in QUEUED...So not fixed yet i guess?
a month ago
Still have the same issue (build: a7b53793)
a month ago
We are still working through backlog so you could be continuing to see some delays. We will update https://status.railway.com/incident/ZLI8N955 when this should not be the case anymore.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 28 days ago