25 days ago
New deployments stuck indefinitely at 'Processing deployment' with all stages 'Not started' (sometimes showing 'queued due to upstream GitHub issues'). GitHub is operational, the Railway GitHub app is authorised for my repo, and redeploying existing builds works but no new deployment from a fresh commit will start building. I've tried cancelling, re-pushing, and disconnecting/reconnecting the repo.
5 Replies
25 days ago
The "queued due to upstream GitHub issues" message can persist even after GitHub itself recovers if the Railway GitHub App has pending permission updates that were not accepted. Go to your GitHub installations, find the Railway app, and accept any pending permission updates. If none are pending, uninstall the Railway GitHub App entirely from that page, then reinstall it from your service settings in Railway and grant it access to your repo. This fully resets the webhook connection and typically resolves stuck deployments that disconnect/reconnect alone does not fix.
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
New deployments stick at "Deployment queued due to upstream GitHub issues" indefinitely and never start building. GitHub is operational (githubstatus.com all green). I've tried: cancelling and re-pushing, disconnecting/reconnecting the repo, and fully uninstalling + reinstalling the Railway GitHub App with repo access re-granted. Redeploying existing successful deployments works fine only new commits hang. The GitHub App shows no pending permission requests.
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
Same with my Depolyment
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
23 days ago
Same here
Status changed to Awaiting Railway Response Railway • 23 days ago
Status changed to Awaiting User Response Railway • 23 days ago
glamorous-zap
Same here
23 days ago
Mine cleared overnight, annoying but might be worth giving it a few hours and trying again.
Status changed to Awaiting Railway Response Railway • 23 days ago
Status changed to Solved Railway • 23 days ago