a month ago
Hi,
My new deployments are stuck in "Queued" and never start. All build/deploy steps show "not started" and no logs are generated at all.
What I've already checked and ruled out:
- Railway status page shows "Fully operational"
- I have credits remaining ($4.93)
- The source branch is correctly set to "main"
- I triggered a Redeploy from the UI → still stuck in Queued
- I pushed an empty commit to force a fresh deploy → still stuck in Queued
Important details:
- My previous (currently running) deployment still works fine — the service is live. Only NEW deployments won't start.
- This started today, shortly after the GitHub incident earlier today. I suspect it may be a leftover inconsistency from that, since Railway pulls my code from GitHub.
Project/service info:
- Project: upbeat-reverence
- Service: web
- The deployment just sits in "Queued" with all stages "not started" and zero logs.
Could you please check the internal state of my project and help unblock the deployment queue? I've exhausted the troubleshooting I can do from my side.
Thank you.
4 Replies
a month ago
Your workspace subscription is currently showing as inactive, which is preventing new deployments from being processed. You can resolve this by visiting your workspace billing page to ensure your subscription is active and your payment method is set up, then resubscribe to the Hobby plan if needed.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Your workspace subscription is currently showing as inactive, which is preventing new deployments from being processed. You can resolve this by visiting your [workspace billing page](https://railway.com/workspace/billing) to ensure your subscription is active and your payment method is set up, then resubscribe to the Hobby plan if needed.
a month ago
Is not inactive, I already checked
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your workspace is set to the Hobby plan but its subscription state is inactive on the backend, with no subscription invoice on record and a $5.00 credit balance (the trial grant). This mismatch, Hobby plan selected but no completed subscription payment, is what prevents new deployments from leaving the queue. You can check and complete the subscription from your workspace billing page.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Mine says I have an active plan (Trial Workspace). Deploys are broken for me too.
Attachments
Status changed to Awaiting Railway Response Railway • about 1 month ago
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