horizonxp
PROOP
17 days ago
Project: journey
Project ID: 0c92aacc-553a-4b77-b944-f276f9b7eafd
Service: journey-app
Service ID: 62404205-6fe1-411a-8f41-615d95d948b8
Fresh deployments for journey-app across production and staging build successfully, push an image, then get stuck in QUEUED with queuedReason "Waiting for deployment slot".
Affected production deployments:
- e7872d5a-0371-45a0-84d1-1e5f18c3a759
- ee8b02bf-6721-4ed0-b13e-769d8f52a815
- db1acd51-0a9b-4ec1-9ddd-67e57ac40cb6
Affected staging deployment:
- 9f942541-1b0b-410a-a7e3-c2720b6a1fc4
Rollback to an existing built image succeeds:
- 19e25f39-30c6-432c-9ec9-160f88930f09
So the current workaround is: do not redeploy latest until Railway resolves this; rollback can keep prod alive.
6 Replies
17 days ago
It should be resolved now, a team member has identified and fixed the underlying issue.
Deploys should go through within the hour.
ourney-managed-daemon-a still has a QUEUED deployment. The pattern is clear: builds succeed but deployments never start.
This is a Railway backend issue. The deployment slot system is broken in your environment. Canceling and retrying won't help if the underlying slot allocation is stuck.
You need to escalate to Railway support immediately:
Contact Railway support at support.railway.com or via your dashboard with:
Project ID: 0c92aacc-553a-4b77-b944-f276f9b7eafd
Environment: production
Issue: Deployments stuck in QUEUED indefinitely; builds complete but never transition to deployment
Affected services: journey-managed-daemon-a, journey-app
Started: ~2026-05-06 00:49 UTC
Status: Persists after multiple cancellations and retry attempts
This requires backend intervention to reset the deployment slot state. There's nothing you can fix from your end.