Deploy stuck in QUEUED ("Waiting for previous deployment") — no active previous deployment exists
mwiechmann
HOBBYOP

17 days ago

Problem

Deployments for my service are stuck indefinitely in QUEUED status with the message "Waiting for previous deployment". However, no previous deployment is in an active state — the deployment history shows only REMOVED entries going back ~7 hours, no SUCCESS or in-progress deployment.

Symptoms

- New deploy stuck in QUEUED with no progress

- "Waiting for previous deployment" message persists even though no deployment is active

- Cancelling the queued deployment and re-triggering reproduces the same stuck state

- Build logs show no errors

What I've tried

- Cancelled the queued deployment and triggered fresh redeploy: same stuck state

Affected deployment

Deployment ID: 84605be1-3591-43e8-808c-467ff723d908

Solved

7 Replies

Status changed to Awaiting Railway Response Railway 17 days ago


calvinmidnatech
PRO

17 days ago

Same Issue here, waiting for slots

"The deployment was rejected before it could start because the workspace had too many concurrent in-progress deployments. This is a transient platform limit, not a code or configuration issue. Retry the deployment after other in-progress deployments in the workspace have completed."

However, I made sure that there's nothing else queued.

projectid:ecb963ee-614c-4b90-af26-e8109ea5ef39


playerzer0x
PRO

17 days ago

Same issue here. Even when switching regions from US West to East.

Project ID: 624dfb3c-860b-464b-b89f-dd7724e27880

Service ID: 4ac0e4fe-e2df-4e27-8753-63241f574108


arquicanedo
HOBBY

17 days ago

Queued for 28:00 minutes and counting. US West, US East, EU West., ... "Waiting for deployment slot"


mwiechmann
HOBBYOP

16 days ago

Seems to work again. Redeploying solved this for me.


15 days ago

Yep, this was a bug that has since been resolved. Sorry about that.


Status changed to Awaiting User Response Railway 15 days ago


diegoklll
HOBBY

15 days ago

infinite queued railway deploy !!!! help pleaseee


Status changed to Awaiting Railway Response Railway 15 days ago


echohack
EMPLOYEE

15 days ago

Hey Diego,

We had a incident where builds were queuing just now, we're seeing that resolve: https://status.railway.com/incident/4T0EQUI1


Status changed to Awaiting User Response Railway 15 days ago


Railway
BOT

8 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 8 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...