New deployments stuck in queue - "upstream GitHub issues" error, only cached redeploys work
nayalish-mahmood
FREEOP

23 days ago

Project: multi-games-arena-backend (production environment)

Issue: Any NEW commit/build gets stuck permanently at "Initialization"

step with message "Deployment queued due to upstream GitHub issues".

Redeploying an EXISTING/already-built deployment works fine (~20 sec).

Tried: disconnecting/reconnecting GitHub source, pushing empty commits —

same result every time. GitHub status and Railway status both show

fully operational.

Stuck Deployment IDs:

  • 0119633a-a0d1-4f64-acb5-d343f251089e
  • 0d1daa88-5b63-4a65-9976-b7a74bd5ae36

Please help unstick the GitHub fetch/build pipeline for this service.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 23 days ago


23 days ago

Your deployments appear to be completing successfully now - the two stuck deployments have been cleared and recent builds are going through. The "upstream GitHub issues" queue state is transient and resolves on its own. If it happens again, fully uninstall and reinstall the Railway GitHub App from your GitHub account, then reconnect the repository in your service settings. You can also trigger a build manually via the Command Palette (CMD/Ctrl + K) and selecting "Deploy Latest Commit".


Status changed to Awaiting User Response Railway 23 days ago


Railway
BOT

16 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 16 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...