2 months ago
Project ID: 02addf56-c426-4e49-a071-8659b3924995
Service ID: 560f253b-87a0-4fbf-ab99-f55c1162ac79 (Scoutly)
Stuck deployment ID: caa8c3b4-d99d-4c7a-88c4-2988ccee73e0
Status: QUEUED since 2026-07-21T18:03:06Z with no build/deploy logs
Pattern: Repeated REMOVED attempts followed by persistent QUEUED, reproducible on redeploy
My deployment remains stuck in QUEUED with “Waiting to start” and no build or deploy logs.
I upgraded the workspace from Free to Hobby, but the deployment remained queued. There is no Limited Access indicator. Cancelling and redeploying reproduces the same issue immediately.
The currently active deployment is healthy and serving traffic. A duplicate service failure shown earlier is unrelated.
Could you please check whether this project’s deployment queue is stuck or locked?
2 Replies
2 months ago
Whelp, it just started after 45 minutes. If you fixed it, thank you!
Status changed to Awaiting Railway Response Railway • 3 months ago
2 months ago
We didn't intervene here - the deployment completed on its own after about 44 minutes in the queue. If you see queued deployments in the future, cancel any stuck ones and redeploy rather than stacking additional attempts, as queuing more deploys can compound the delay.
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved sam-a • 3 months ago