The "Deployment queued due to upstream GitHub issues" message indicates a temporary disruption in the connection between Railway and GitHub's API. Cancel any queued deployments and avoid triggering new ones for now, as additional deploys can compound the queue. Once the connection stabilizes, your deployments will process normally.

Thanks, but this isn't resolving with that guidance. I've already:

Cancelled all queued deployments multiple times

Waited well over an hour without triggering new deploys in between

Fully disconnected and reconnected my GitHub account (not just the repo)

Disconnected and reconnected the repo itself in service settings

Every fresh attempt after these steps still gets stuck in "Queued" with the same "upstream GitHub issues" message, or now shows "Processing deployment..." indefinitely. This doesn't look like a transient API blip on my end — could someone check the backend pipeline for project b169cd7d-af09-4975-bcb8-39dbef60bc47 (environment fbcb2e9c-244d-417a-b589-858e743803f5)? I need a working deployment to ship a fix that's currently blocked.

Update: I got a working deployment through by using the Railway CLI (railway up) to deploy directly from my local machine — that one shows Active/"Deployment successful" now, so the app itself is live and running the latest code.

For context on the pattern: the first deployment that got stuck ("retrigger deploy 2") did eventually complete and go Active on its own after sitting in "Queued" for a while, without me doing anything further. But the very next push after that ("Make admin dashboard header a home link") got stuck the same way again, and this time did not resolve itself — I had to fall back to the CLI to get it deployed.

So the underlying problem is still unresolved: GitHub-triggered deployments (i.e., the normal auto-deploy that should happen on every git push) are unreliable for this project — sometimes clearing on their own, sometimes not, with no clear pattern. This happens even though:

The GitHub connection under Settings → Source Repo shows healthy (repo connected, main branch linked, auto-deploy enabled, no warnings)

I've disconnected/reconnected both the repo and my GitHub account entirely

The CLI-based deploy of the exact same code works without any issue every time

This strongly points to something broken specifically in the GitHub webhook/build-trigger pipeline for this project, not a problem with my repo, code, or account connection. I don't want to have to manually run railway up after every single push going forward — could your team investigate why GitHub-triggered deployments aren't reliably reaching the build queue for this project?

Project ID: b169cd7d-af09-4975-bcb8-39dbef60bc47

Environment ID: fbcb2e9c-244d-417a-b589-858e743803f5

Thanks for the detailed timeline, it actually matches the root cause exactly. This was a backlog in our own deploy queue for trial and free workspaces today (the "upstream GitHub issues" message was misleading). The queue partially drained and then backed up again, which is why one push eventually went through on its own while the next one got stuck. GitHub-triggered deploys go through that queue, while railway up bypasses it, which is why the CLI worked every time.

The backlog is now fully cleared, so there is nothing broken in your project's webhook or build pipeline, and you should not need the CLI workaround going forward. Your CLI deploy from 19:12 UTC is live. Next git push should auto-deploy normally; if it gets stuck again, reply here and we will investigate.

it’s happening again

Sorry this is back, you should be good to try again now. Apologies for the disruption.

I am now running into this issue.

Hi, I just took a look and you should be good to deploy freely now.

Are you still seeing deploys queued? This does happen occasionally for hobby and trial users if we're experiencing more than the normal build volume.

Thanks, I just triggered a redeploy manually and it worked fine.