Subject: GitHub deploys failing with ##FORBIDDEN## repository forbidden — wrong installation mapping?

Service: painel-magnun (production)

URL: painel-magnun-production.up.railway.app

Repo: jonascamporez-art/painel-magnun

Every GitHub-triggered deploy fails at "Initialization > Snapshot code" with:

[ERROR] ##FORBIDDEN## repository forbidden

Settings → Source shows the repo as connected, but under "Branch connected to

production" it shows: "Resource not accessible by integration".

What I already checked and tried:

• Railway GitHub App is installed on jonascamporez-art with "All repositories"

  access and read/write permissions on code, deployments and metadata.

• Disconnected and reconnected the source repo (multiple times).

• Reselected the repo from the dropdown — the repo IS listed and selectable.

• Manual redeploy from the dashboard works, but it only replays the cached

  snapshot, so new commits never reach production.

My suspicion: there is a second Railway GitHub App installation on the

sistemasinvest-lab organization, created recently around the same time this

broke. I believe this service is mapped to the wrong installation_id — the repo

belongs to jonascamporez-art, not to that org, which would explain a valid

installation returning "resource not accessible" for this specific repository.

Could you reset / re-map the GitHub App installation for this service on your

side? Disconnecting and reconnecting from the dashboard does not fix it.

Thanks.