a month ago
Deploys on my project have been stuck in a QUEUED state for the past ~30 minutes, all showing the same reason: "Deployment queued due to upstream GitHub issues." Every stage (Initialization, Build, Deploy, Post-deploy) stays at "Not started."
What I've already tried, with no change:
Removed the stuck deployments and let it re-trigger from a fresh push
Disconnected and reconnected the GitHub integration for this service
Toggled Auto Deploy off and back on
Pushed multiple new commits to main since — every single one queues with the identical message within seconds of the push landing on GitHub
Why I don't think this is actually a GitHub-side issue:
githubstatus.com shows all systems operational, including Git Operations, Webhooks, and Actions
status.railway.com also shows fully operational, including "GitHub — Auto-Deploys" at 100% uptime today
The pushes are confirmed present on GitHub (verified via git fetch/git log against origin/main) — the repo side is fine
Details:
Project/Service: 2d92bc5e-d30c-4e93-a183-0bea22abd918
Environment: production
Commits currently stuck: db8e9a28
Last known good deploy: 1f8aef80
Given both status pages are green and the local remediation steps (reconnect/toggle/re-push) haven't helped, this looks like a stuck state on Railway's backend for this specific project rather than an actual GitHub outage. Could you take a look at what's blocking the queue?
4 Replies
a month ago
Your workspace's subscription is currently in an INACTIVE state with no active billing on file, which will prevent deployments from processing. The $5.00 balance showing is the standard trial credit. You can resubscribe to the Hobby plan from your workspace billing page, and once the subscription is active, queued deployments should proceed normally. Cancel any currently stuck deployments first to avoid compounding the queue when things resume.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
I have the same issue. I upgraded to the hobby plan. my deployment is still stuck.
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Yes - it's not related to Hobby plan. I still have credits on FREE plan.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
okay after upgrading and deleting the old commits it worked on the next push
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