a month ago
When I try to deploy my latest commit it goes straight to queued in railway citing a github issue upstream. I can't see any issues on the github side and i've also tried disconnecting and reconnecting the railway/github link. This occurs on both production and staging.
This was generated by your AI tool:
Service ID: 526e3e8f-deb4-4b78-8ad4-2090a7254ffb
Affected deployment IDs: 949cc838-ecea-43b5-b0be-54b5a5648cec, 9f12c12a-4c23-4723-a033-a3c7cb713d51, 8e4017b7-4131-4abb-b29d-84a2a1f10e46
Repo: ryanv11/travel-tracker (main branch)
That you've attempted multiple redeploys without resolution
No build logs are being generated, and diagnostics show no error—just persistent QUEUED status
This is a platform-level issue that needs Railway's team to check the GitHub integration or deployment queue system.
6 Replies
a month ago
Your workspace subscription is currently in an inactive state, which is why deployments are staying in the queue rather than building. This isn't a GitHub integration issue. You can resolve this by visiting your workspace billing page to complete your subscription setup, and deployments will process normally after that.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
I also checked my account and it appears to be active.. however i'm just on the trial version, I signed up about 2 hours ago.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
It says that I have an active plan when looking at the workspace billing page?
Attachments
a month ago
To correct my earlier message, this is not a subscription setup issue. Your trial credit is fully intact at $5.00 and your billing page correctly shows an active trial, so deployments should not be blocked by billing state. Please try a hard refresh of the dashboard (Ctrl/Cmd + Shift + R) or log out and back in, then attempt a new deploy and let us know if it goes through.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
I still have the same issue after multiple hard refreshes and logging out and back in. I've cleared all of the deployments that were queued and tried to deploy the latest commit and it's still in queued with the same upstream github issues error and no logs.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This wasn't a GitHub or billing issue. Earlier today we had an upstream GitHub incident, and while we recovered, deploys on trial workspaces were temporarily queued behind paid plans. That throttling has since been lifted and your deploys are flowing again. Your latest deployment completed successfully about an hour ago.
One note: the deploy from 19:15 UTC built fine but crashed on startup, so if you saw a failure there, check that deployment's logs.
Apologies for the earlier replies pointing at your subscription, that was incorrect. Your trial is active with full credit.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved sam-a • about 1 month ago