Project: zesty-mindfulness

Service: PRD011_DATA_-_-2

Repo: aimoaiteam-netizen/PRD011_DATA_-_-2 (private)

Builder: Dockerfile (services/api/Dockerfile)

Problem

GitHub webhook auto-deploys fail at the snapshot stage with:

"[ERROR] ##NOT-AUTHORIZED## repository not authorized"

The service Settings → Source also shows "Bad credentials" under

"Branch connected to production".

Timeline (all times approximate, today)

• ~2h ago: last SUCCESSFUL deploy via GitHub (commit 315e233).

• ~1h ago: next commit (48cec17) → Railway received it but the deploy

  FAILED with "repository not authorized".

• After that: subsequent commits (a3e49cd, 6827a31, b6cd8cf) are NOT

  received by Railway at all — no commit status is posted to GitHub,

  and no deployment is created. (Vercel, connected to the same repo,

  deploys all of these commits fine, so the repo and GitHub itself are healthy.)

What I've already tried (none fixed it)

• Uninstalled and reinstalled the Railway GitHub App (Installed GitHub Apps)

• Set Repository access to "All repositories"

• Revoked Railway under "Authorized GitHub Apps" and re-logged in /

  re-authorized (user-to-server token refreshed)

• Disconnected and reconnected the Source repo in the Railway dashboard

  multiple times

• Confirmed GitHub App permissions are correct (read/write on code,

  deployments, etc.)

• I did NOT change my GitHub password or 2FA.

After all of the above, "Bad credentials" persists and webhook deploys

still don't trigger.

Suspected cause

This matches an existing report:

https://station.railway.com/questions/webhook-deploys-failing-with-repository-916ce49d

i.e. a STALE INSTALLATION ID cached at the project level on Railway's side,

which a GitHub App reinstall does not refresh.

Request

Please reset / refresh the cached GitHub installation ID for this project

(zesty-mindfulness / PRD011_DATA_-_-2) on your backend so webhook deploys

and the source connection work again. The service is currently Online on

the last good deploy (315e233), so there is no downtime — only new deploys

are blocked.

Thank you!