Hi Railway team,

After uninstalling/reinstalling the Railway GitHub App, ALL of my services

that connect to GitHub now show "Bad credentials" and cannot auto-deploy.

This is account-wide, not one service. I believe the reinstall left my

account pointing at a stale/orphaned GitHub App installation_id that the

dashboard can't fix. Please reset the GitHub integration state for my

account and re-link it to the current installation.

— Account / identifiers —

Railway login email:

GitHub account: btclending (personal account, not an org)

Affected: ALL GitHub-connected services on this account

Project ID (one example): <PROJECT_ID>

Service (example): WingmanPro Backend (Service ID: <SERVICE_ID>)

Environment: <ENVIRONMENT_ID> (production)

Repository (example): btclending/wmp-app-fork (private), branch main, root /backend

— Timeline —

1. I repointed one service's Source Repo from btclending/wmp-api-fork to

   btclending/wmp-app-fork (two repos merged into a monorepo).

2. That service showed "Auto deploy unavailable" → tooltip

   "No project member has access to this GitHub repository," even though the

   App had All-repositories access and my other services deployed fine.

3. On support-doc guidance I uninstalled + reinstalled the Railway GitHub App

   and revoked/re-authorized OAuth. Now EVERY GitHub-connected service shows

   "Bad credentials."

— What I've already verified / tried —

• Railway GitHub App reinstalled on btclending with All-repositories access

and full read/write perms; no pending permission updates.

• Revoked Railway under GitHub Authorized OAuth/GitHub Apps and re-authorized.

• Disconnected/reconnected repos, re-set source/branch/root, waited for cache.

• I have ADMIN on the repos; they are private.

• Still account-wide "Bad credentials."

My read: the reinstall created a new installation_id but my account record

still references the old one, so GitHub calls 401 across all services.

Please reset/re-link my account's GitHub integration. Happy to provide any

additional IDs privately.

Thanks — this is affecting all my production services' ability to deploy.