a month ago
Service: blueroses_server
Environment: production (ID: 24f7e16a-eb75-4434-92b1-6549dc4984e5)
Project: beneficial-surprise (ID: 020a795b-73df-4146-b127-e535d0255ff1)
Two deployments are stuck in QUEUED status and not starting the build:
- Deployment 1: db240368-8ec3-4d12-b300-825aee68c95f (18:36:05)
- Deployment 2: eb9c1138-01dc-4301-ac81-d0de0f0c928a (18:37:42)
Both have been queued for several minutes without any progress. No configuration errors detected, the status simply doesn't change from QUEUED.
Repository: itzrealman/blueroses_server (main branch)
Region: sfo
Builder: Railpack
Why are the deployments stuck in the queue and not progressing to the build stage?
3 Replies
a month ago
Your workspace is on the Hobby trial, and during periods of high platform traffic, builds for Hobby-tier workspaces can be temporarily queued while Pro/Enterprise workloads are prioritized. You can cancel the stuck QUEUED deployments from the deployment menu (click the three dots next to each deployment and select "Abort"), then trigger a fresh deploy once the queue clears.
Status changed to Awaiting User Response Railway • 30 days ago
a month ago
When is it expected approximately?
Status changed to Awaiting Railway Response Railway • 30 days ago
a month ago
There's no specific ETA we can give for this. We'd recommend cancelling the stuck queued deployments and waiting rather than triggering new ones, as additional deploys can compound the queue.
Status changed to Awaiting User Response Railway • 30 days ago
23 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 • 23 days ago