Deployment stuck in queued state
safeguard0703
FREEOP

a month ago

My deployment is stuck in the internal queue and the build never starts.

Deployment ID: 3593e60d-9b7c-44ac-b32d-bce8bb774be1

Service: safeguard

Commit: 655e60f

Domain: api.safeguardscan.com

Railway receives the GitHub commit and creates the deployment, but it stays in Queued / Processing deployment.

Build logs are empty and show "Waiting for build to start".

Could you please check whether this deployment is stuck in the internal builder queue and help restart or clear it?

Solved

1 Replies

Railway
BOT

a month ago

Your workspace's Hobby subscription is currently inactive, which is why the deployment stays queued and the build never starts. You can reactivate by subscribing from your workspace billing page, and the queued deployment should proceed once the plan is active.


Status changed to Awaiting User Response Railway about 1 month ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...