3 months ago
Problem: The Development service is stuck in a perpetual QUEUED deployment state with no build or deploy activity occurring. Despite multiple code pushes and configuration changes, deployments never progress beyond QUEUED status.
Service Details:
Service: Development
Service ID: 91434ae3-a213-4056-9247-a72c4f1b2a59
Environment ID: e68b0386-cf78-4e40-a366-217a793df0b6
Project ID: 7fd00754-d64f-4208-a749-6cca77aea1d0
Current Stuck Deployment:
Deployment ID: 8bbf4b48-0d8e-4bf8-a190-0164794124c7
Status: QUEUED (stuck since 2026-07-11 19:33:43 UTC)
Commit: a0fe00d6ede2e748307ef73d82041e3c491ff26a
No build logs, no errors, no active replicas completely frozen
Observed Behavior:
Code pushes trigger the build process (Docker image builds and pushes successfully)
Build completes without errors
Deployment immediately enters QUEUED state
Deployment never transitions to BUILDING, PUBLISHING, or SUCCESS
No logs appear for the QUEUED deployment
Service status shows "Deploying" but no activity occurs
Previous 10+ deployments all marked REMOVED instead of FAILED or SUCCESS
Troubleshooting Attempted:
Fixed service configuration (reference variable mismatch with database credentials)
Disabled auto-deploy to prevent queue buildup
Verified code repository is accessible and builds complete successfully
Confirmed no active running deployments blocking the queue
Confirmed service config has no errors
Impact: The Development service is non-functional. Any code changes cannot be deployed due to the queue deadlock. This appears to be a platform-level issue with the deployment queue system, not a service configuration problem.
Request: Please investigate and manually clear the deployment queue for this service. The queue appears to be in a deadlocked state where deployments are created but never processed.
3 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
You were right, this was a deadlock on our side. A deployment from earlier today was replaced in the dashboard but its backing process never actually stopped, and it kept holding your service's deploy queue. Every deploy after it waited on that ghost, which is why they all sat at QUEUED and then showed as REMOVED.
We've cleared the stuck process and redeployed your latest commit, and it went live successfully a few minutes ago. New pushes will deploy normally now. Sorry for the lost afternoon.
Railway Team
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved sam-a • 3 months ago
3 months ago
Hi this is now doing the same after we started again this morning. Please may you guys fix it and is there anything that can be done to stop this happening again please as is stopping us in our tracks everytime it happens.
Attachments
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Cleared again and your latest commit is now live.
This is the same platform bug as yesterday, not anything wrong with your setup. A deploy from this morning didn't release its slot in the deploy queue, so everything behind it sat at QUEUED. It's a known issue on our side and there's a fix in progress.
Unfortunately there's no setting on your end that prevents it, and it could happen again. If it does, the signal is a deploy stuck at QUEUED with no build or deploy logs. Reply here (or start a new thread) and we'll clear it quickly, usually within a few minutes once we see it. You won't lose any code, the stuck deploys just need us to release the queue.
Sorry this keeps interrupting you. We know manual clears aren't a real fix and we're pushing on the underlying bug. If you see it again, reply on this thread for the fastest response to ensure we have the full context.
Railway Team
Status changed to Awaiting User Response Railway • 3 months ago
2 months 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 • 2 months ago