Project: fulfilling-optimism (project ID: b705691c-8a6d-4c33-9145-449c2415e931)

Service: stock-briefing-tool (service ID: 0d038d51-b65a-44a4-a6f9-17ad4906a9e8)

Environment: production

What happened:

My GitHub repository was renamed from stock-briefing-tool to stock-briefing-backend1 (still under the same owner, joshuamost726-dot). Since then, every deployment triggered by a GitHub push gets stuck permanently in "Queued" status with the message:

▎ "Deployment queued due to upstream GitHub issues"

It never progresses past that — Initialization, Build, Deploy, and Post-deploy all remain "Not started."

What I've already tried:

1. In the service's Settings tab, I saw "GitHub Repo not found" under Source Repo. I clicked Disconnect and reconnected, re-selecting joshuamost726-dot/stock-briefing-backend1. The error message disappeared from the UI, but every deployment triggered afterward (multiple test pushes) got stuck with the exact same "upstream GitHub issues" message.
2. I checked the Railway GitHub App installation on GitHub's side (github.com/settings/installations) — Repository access is set to "All repositories" (not restricted to specific repos), and there's no pending permission-approval banner. So this doesn't appear to be a GitHub-side permissions/scoping issue.

Current workaround: I'm deploying manually via railway up from the CLI, which works fine — but GitHub auto-deploy needs to work again for my normal workflow.

Ask: Could you check on Railway's side whether this service's GitHub connection properly re-synced after the repository rename? It looks like something may not have fully updated internally even though the UI shows the repo as connected.