Description of the issue:

My backend service (Python/FastAPI) has multiple deployments stuck in "Queued" state, each showing "Deployment queued due to upstream GitHub issues." Instead of resolving, new pushes are creating additional stuck queued entries rather than replacing the earlier ones — I now have 3 separate queued deployments for effectively the same commit, piling up over 8+ minutes.

Error messages and descriptions:

"Deployment queued due to upstream GitHub issues" — shown under each queued deployment in the Deployments tab.

Logs (build and/or deploy):

No build logs are generating yet since the deployments are stuck in the queue before reaching the build stage.

Link to GitHub repo:

https://github.com/vineetsangwan/truecreds

Branch: main

Additional context:

• I checked status.railway.com and it currently shows "Fully Operational" with no acknowledged incident, so this doesn't appear to be a known widespread outage.
• My currently ACTIVE deployment (from before this issue started) is still running fine and serving traffic — so the site itself is not down, just new deployments aren't going through.
• I recently added a Watch Paths setting (backend/**) to this service shortly before this started — not sure if related, flagging in case it is.
• Tried: nothing yet beyond waiting — about to try "Deploy Latest Commit" from the Command Palette next.