Project: order-processing-wms

Environment: production

Service: order-processing-wms (order-processing-wms-production.up.railway.app)

Repo: bombayonsale-ux/order-processing-wms, branch: main

Issue:

Deployments triggered by GitHub pushes are stuck in "QUEUED" status and never progress past Initialization (Build/Deploy/Post-deploy all show "Not started"). The deployment details panel shows the message: "Deployment queued due to upstream GitHub issues."

Timeline:

First noticed: Jul 27, 2026, ~5:22 PM GMT+5:30

Affected deployment(s): commit 29e39949, and a later empty commit (ea4c0bb) pushed specifically to retrigger — both stuck in the same state

One earlier deployment did complete successfully before this started (commit fa255d3)

Already checked/tried:

GitHub API/webhooks show no outage on githubstatus.com

Pushed a fresh empty commit to main to force a new deployment — same "queued due to upstream GitHub issues" result

No changes made to the GitHub App installation or repo permissions on our end

Ask:

Please check whether Railway's GitHub App connection/webhook for this repo has lost access or hit a rate limit, and help restore normal auto-deploy on push. Happy to provide the deployment ID(s) or logs if needed.