Skip to content
stuck in QUEUED
bloodfang
OP

23 days ago

Hello Railway Support,

My deployments have been stuck in the QUEUED state for over 9 hours. The builds never start.

Could you please investigate whether there is an issue with my deployment queue?

Thank you!

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 23 days ago


dizzydes90
EMPLOYEE

23 days ago

Your queued deployments are all waiting on one earlier deployment of the same service. That deployment started at 17:36 UTC on October 27 and has been stuck in its pre-deploy step for about 18 hours, and twelve newer deployments of that service are lined up behind it, each waiting for the previous one to finish.

The logs for that stuck deployment show it starting a gunicorn web server on port 8080. A server keeps running until stopped, and a deployment held in its pre-deploy step does not move on while that step is still running. Cancelling that stuck deployment from the service's deployments list lets the queue behind it proceed.

Before redeploying, make sure the service's pre-deploy command only runs a task that finishes and exits (such as a migration), since starting the web server belongs in the start command, which is currently bash start.sh.


Status changed to Awaiting User Response dizzydes90 • 23 days ago


Railway
BOT

16 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 • 16 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...