25 days ago
I've been unable to deploy for over 50 minutes. Multiple deployments are stuck in QUEUED status and not progressing to BUILDING.
Project: ravishing-forgiveness (d08e14e1-024a-4944-948c-72dcf96d3d6a)
Environment: production (961e6de5-b35c-473d-9dc7-b135a276cf20)
Service: Pruebas Regresion QA OnnetFibra (d7584780-a85d-4f31-99c0-a157c592034c)
Stuck deployments:
- 5702b0c9-a92b-4810-a206-f2d2ffdb3202 (created 19:51 UTC, 2026-07-27)
- c2141070-da9e-493e-b7f7-511fb6db1b32 (created 20:09 UTC, 2026-07-27)
One deployment did complete successfully (29134f81-83e5-4024-808d-0ebfa4a49065 at 20:02:28 UTC), but the queue appears to have stopped processing after that.
This is clearly a Railway infrastructure/queue issue, not a code or configuration problem. The deployments are not even entering BUILDING stage.
Please restart the deployment queue or investigate what's blocking it.
1 Replies
25 days ago
Your workspace is on the Hobby plan (currently in trial), and the latest deployment on this service is confirmed stuck in QUEUED status since 20:09 UTC. Hobby and Trial tier deployments can be temporarily queued during periods of high platform demand, as documented under Limited Access. The recommended workaround is to cancel the stuck queued deployments from the deployment menu and trigger a fresh deploy rather than stacking additional deployments behind them. If you need deployments to always process immediately regardless of platform load, upgrading to the Pro plan bypasses this queue.
Status changed to Awaiting User Response Railway • 25 days ago
18 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 • 18 days ago