GitHub auto-deploy not triggering after repo transfer + App reinstall — service stuck on 4-day-old commit
mathieuhenry21
HOBBYOP

a month ago

Hi Railway team,

My GitHub integration stopped auto-deploying after I transferred the source repository to a new GitHub account. Manual CLI deploys (railway up) work fine, so the project is healthy — but pushes to the connected branch are completely ignored.

Project info

  • Project ID:eb3388dd-1543-4501-8db6-fcda962857ea (thirsty-wine-club)
  • Service ID:0a5f1cb1-99f0-4a60-ae20-c5a70c0379a4 (web, production env)
  • Current live commit: 4 days old (auto-deployed before the repo transfer)
  • Expected commit:df80066 on branch main

Repo info

  • Previous URL:github.com/BurgundyDiscovery/thirsty-wine-club-shipping
  • Current URL:github.com/mathieuhenry21/thirsty-wine-club-shipping (private)
  • Branch connected in Railway:main
  • Source Repo shown in Railway Settings:mathieuhenry21/thirsty-wine-club-shipping

Timeline

  1. Yesterday morning:git push origin main → auto-deploy worked normally.
  2. Yesterday afternoon: Repo renamed/transferred from BurgundyDiscovery to mathieuhenry21.
  3. Since then: 4 pushes (c59541e, 9ab54c3, df80066, empty commit trigger deploy) — none triggered a Railway deploy.

What I tried

  • Disconnect/Reconnect the source repo in Railway Settings (multiple times)
  • Branch disconnect/reconnect
  • Uninstalled the Railway GitHub App from mathieuhenry21/settings/installations, then reinstalled it via Railway's "Connect Repo" flow
  • Reconnected Account-level GitHub OAuth in Railway Account Settings
  • Pushed an empty commit to force webhook
  • All of the above while EU West builds backlog incident was ongoing (now resolved)

My hypothesis

Railway's internal record of my project likely still references the old GitHub App installation_id (from the BurgundyDiscovery account) or the old repo full_name. When the new installation sends webhook events, Railway doesn't match them to my project → no deploy triggered.

Request

Could you please re-link my service 0a5f1cb1-99f0-4a60-ae20-c5a70c0379a4 to the current GitHub App installation on mathieuhenry21? The UI shows the correct repo, but the backend clearly doesn't receive/process the events.

Happy to provide any additional info (installation IDs, specific commit SHAs, logs).

Thanks!

Mathieu Henry — mathieu.henry.leveur@gmail.com

Solved

1 Replies

timomeh
EMPLOYEE

a month ago

Hi, thanks for the report. I'm on the Product Engineering Team and looked into this issue.

Could you once again try to disconnect and reconnect the repo from the service?

We had issues with some GitHub Webhooks getting blocked, which caused that our system had stale data for a few hours, and it referenced your old GitHub Installation. The old GitHub Installation of course can't access the new transferred repo anymore. From our logs, I can see that your attempt to reconnect the repo was before our data was updated.

We now fixed the underlying issue of GitHub Webhooks getting blocked, to prevent similar issues in the future.

It would be great if you could report back if reconnecting solves your issue. Thanks! -Timo


Status changed to Awaiting User Response brody 26 days ago


Railway
BOT

18 days 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 18 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...