Skip to content
App deployment stuck in queue with no associated build
anirban0019
OP

20 days ago

My straya_sports deployment has been stuck at Queued → Processing deployment for over an hour. Initialization hasn’t started, and the CLI reports “Deployment does not have an associated build.”

I’ve tried cancelling the queued deployment and deploying the latest GitHub commit again, but the issue persists. A queued backup deployment proceeded after cancelling the original app deployment. Temporarily disabling the backup cron hasn’t resolved the app’s queue delay.

The previous app release remains online and healthy.

Could you investigate whether a stuck scheduler entry, concurrency restriction, or capacity pause is blocking this service? Please preserve the currently running deployment.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 20 days ago


Railway
BOT

20 days ago

Your workspace isn't hitting its concurrency limit. None of its 3 build/deploy slots are in use, and the only deployment waiting is the straya_sports one created at 08:03 UTC. The backup cron and your plan limit aren't what's holding it back.

There is also no deploy pause on your plan. The current recovery work from the October 21 incident only affects new signups.

The queued deployment hasn't started building yet, so the CLI says it has no associated build. We haven't found the reason it isn't moving out of the queue.

While it waits, it hasn't replaced anything. Your previous release is still the active deployment.


Status changed to Awaiting User Response Railway • 20 days ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...