We've confirmed your account and workspace are active. The "No repositories found" issue when the GitHub App is already installed with full access typically means the GitHub connection on the Railway side needs to be relinked. Go to Account Settings and disconnect your GitHub account entirely from Railway, then reconnect it and re-authorize the OAuth flow - this re-syncs the repository list with your GitHub App installation.

Tried Reconnect from Account Settings. Still 'No repositories found' when searching. Can't find any repos including ones that were connected before. The GitHub App is installed (1 hour ago), All Repositories access, OAuth reconnected. Search returns nothing for any repo name. Need a human to look at the account-level GitHub token.

CLI login works via browserless pairing. API token auth fails ('Invalid RAILWAY_TOKEN') even with a freshly created token. GitHub repo connection still shows 'No repositories found' when trying to Connect Repo in service settings. Browser-based railway login also fails. Only browserless CLI auth works. Something is fundamentally broken with the OAuth/token layer on my account.

A few things to check here. For the GitHub connection, make sure the GitHub account linked to Railway (visible at railway.com/account) is the same GitHub account where the Railway App is installed. If you have multiple GitHub accounts, this is a common mismatch. For the API token, make sure you're copying the full token from railway.com/account/tokens with no extra whitespace, and using it as RAILWAY_TOKEN in your environment (not as a service variable). For browser-based CLI login, try a private/incognito window to rule out extensions or cached sessions.

Thanks Brody — the GitHub auto-deploy webhook is actually working now, builds trigger correctly on push.

The new issue is that Railway is no longer posting deployment status updates back to GitHub. Our repo's Deployments section (github.com/claudebot001/flipster-dispo-suite → Deployments) is stuck at 228 and hasn't updated since yesterday morning, even though we've had 10+ successful deploys since then via the GitHub webhook trigger.

So inbound (GitHub → Railway trigger) works

But outbound (Railway → GitHub deployment status) not firing

Thanks Brody — the GitHub auto-deploy webhook is actually working now, builds trigger correctly on push.

The new issue is that Railway is no longer posting deployment status updates back to GitHub. Our repo's Deployments section (github.com/claudebot001/flipster-dispo-suite → Deployments) is stuck at 228 and hasn't updated since yesterday morning, even though we've had 10+ successful deploys since then via the GitHub webhook trigger.

So inbound (GitHub → Railway trigger) works

But outbound (Railway → GitHub deployment status) not firing

Can you please open a new thread for that issue.