a month ago
Service: web
Deployment ID: e7f6697b-4e87-4bf8-8ef8-c809db090d38
Our production deploys on the "web" service are stuck in QUEUED and never
transition to BUILDING — empty build and deploy logs, zero activity. The
deployment above (e7f6697b-4e87-4bf8-8ef8-c809db090d38) is the one currently
wedged in the queue.
We have cancelled and re-triggered several times, and also pushed fresh commits
to the production branch (master), but every new deploy reproduces the same
wedge: it just sits in QUEUED and never picks up a builder. The previously
deployed version is still serving live traffic fine, so the running app is
healthy — only new deploys are affected.
GitHub is fully operational on our side (githubstatus.com is all green), so this
is not an upstream GitHub problem, despite the "queued due to upstream GitHub
issues" message shown in the UI.
This looks like the known deploy-queue deadlock (a previous deploy not releasing
its queue slot). Could you please manually release the stuck deploy-queue slot
for this service? Once cleared, our latest commit (f00e23e on the master branch)
should build and go live. Thank you!
1 Replies
a month ago
Your workspace's Hobby subscription is currently in an INACTIVE state, which is why new deploys are sitting in the queue and not picking up a builder. You can reactivate your subscription from your workspace billing page, and once the plan is active again, queued deploys should process normally.
Status changed to Awaiting User Response Railway • about 1 month ago
24 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 • 24 days ago