2 months ago
My just-enthusiasm service has two deployments stuck in QUEUED status for an extended period and neither will progress:
Deployment ID: b2dd5ff0-d2cd-4dc0-99d8-3c8f2395263f (created 2026-07-27T19:36:59.515Z)
Deployment ID: 8b2514ce-e580-4de4-857d-814df3f7f399 (created 2026-07-27T19:18:06.519Z)
Commit: 8b2fa31756183dce5590fae1190b9a9d38dbf5a9
Branch: main
Attempted to trigger a new deploy thinking it would clear the first one, but now both are stuck queued. Restart failed because there's no active deployment. The queue appears blocked at the platform level.
Project: triumphant-connection (ID: 21b7f0f7-5315-4993-94b7-2c5950632d98) Environment: production (ID: 5713c43e-0c58-4471-ba71-c731425cff9b) Service: just-enthusiasm (ID: 5ea907a2-b7d9-40f7-b6dd-6e4e99f9b67d)
1 Replies
2 months ago
Your workspace is on the Hobby trial, and during high-traffic periods we temporarily pause builds for Free and Hobby tier users while Pro/Enterprise workloads are prioritized. Your queued deployments will automatically process in order once the pause lifts. You can cancel the stuck queued deployments from the deployment menu (three-dot menu on each deployment, then "Abort" or "Remove") so only a single fresh deploy is queued when the queue clears. If you need to deploy immediately, upgrading to the Pro plan bypasses the deployment queue entirely.
Status changed to Awaiting User Response Railway • 2 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