Skip to content
GitHub auto-deploy broken across multiple projects — "No GitHub installation found for repo"
corsomtam-sketch
OP

3 months ago

Account: [email protected] (corsomtam-sketch)

Service (representative example, still failing): pretty-creativity / polymarket / production

Also affected: outstanding-healing / finallyai-insta-slides / production (currently FAILED); bnb-compounder / bnb-compounder / production (failed 3x on 2026-08-22, 08-25, 08-28, worked around via manual railway up)

Unaffected: news-to-content-queue's two services deploy fine

Issue: Pushes to main are no longer triggering auto-deploys on multiple projects in this account. On bnb-compounder, the last 3 deploy attempts failed with no build/deploy logs at all (deployment history shows "Initialization: Not started"). Running railway redeploy --from-source via CLI returns:

No GitHub installation found for repo: corsomtam-sketch/bsc-compounder

What I've already checked/tried:

  • GitHub → Settings → Applications → Installed GitHub Apps → Railway App: installed 5 months ago, repository access set to "All repositories" — not scoped/restricted.
  • Disconnected and reconnected the bnb-compounder service's Source repo in the Railway dashboard — did not fix it, same error persisted.
  • Confirmed via status.railway.com there's no active incident affecting GitHub Auto-Deploys.

Impact: Multiple projects on this account can no longer deploy via GitHub push. Currently working around it project-by-project with railway up (manual CLI deploy), which isn't sustainable.

Please check this account's stored GitHub App installation reference on Railway's backend — this looks like a stale/invalid installation ID or token, not a per-repo config issue, since it's affecting several unrelated projects at once.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 3 months ago


sam-a
EMPLOYEE

3 months ago

We confirmed the "No GitHub installation found" error is consistently hitting the token acquisition step across your repos, which is why deployments never initialize. The repo-level disconnect/reconnect you already tried is narrower than what is needed here. Go to your Railway account settings, unlink the GitHub integration entirely, then relink it. If that does not resolve it, go to GitHub Settings, Applications, Installed GitHub Apps, remove the Railway App completely, then reinstall it from the Railway account page and grant it access to all repositories again.


Status changed to Awaiting User Response sam-a • 3 months ago


Railway
BOT

2 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 3 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...