Github Integration Stuck, Can't Auto Deploy
makgabri
FREEOP

19 days ago

All repositories show “Auto deployment unavailable,” despite my Railway account being linked to my GitHub, the Railway GitHub App having repository access, and reconnecting the service source.

Saw a similar post where the github app installation id was referencing the incorrect one and therefor could not properly auto deploy.

Similar problem I faced: https://station.railway.com/questions/git-hub-source-reconnect-stuck-f1a0f888

$10 Bounty

4 Replies

Railway
BOT

19 days ago

The troubleshooting steps in our docs cover this: first accept any pending permission updates on the Railway GitHub App, then try disconnecting and reconnecting the repo in your service settings, and if that doesn't resolve it, use the project canvas Add > GitHub Repository > Refresh to force a cache refresh. If the issue persists after those steps, uninstall and reinstall the Railway GitHub App entirely.


Status changed to Awaiting User Response Railway • 19 days ago


makgabri
FREEOP

19 days ago

Clicking refresh, uninstalling and reinstalling the the integration on github doesn't resolve the issue. I have tried those options already.


Status changed to Awaiting Railway Response Railway • 19 days ago


Railway
BOT

19 days ago

Your service source shows the repo and branch connected correctly at the config level. With the documented troubleshooting steps already exhausted, could you confirm whether the "Auto deployment unavailable" message appears on all services in your project, or only this one? Also, when you reinstalled the GitHub App, did you grant access to all repositories or only select ones?


Status changed to Awaiting User Response Railway • 19 days ago


makgabri
FREEOP

19 days ago

It appears on all repositories.


Status changed to Awaiting Railway Response Railway • 19 days ago


Railway
BOT

19 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 19 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...