10 hours ago
Original GitHub owner account was removed from our org. Reinstalled Railway App on SedgeAI org (code/deployments read+write confirmed, repo selected), fully disconnected+reconnected GitHub on my Railway account as new owner. Still get 'Failed to fetch repository files' + 'auto-deploy unavailable / no project member has access.'
I've confirmed the GitHub App on the org has Contents/Deployments read+write and the repo selected; deploys via railway up (CLI/project token) work fine — only the GitHub-triggered path is broken.
The SedgeAI installation seems orphaned to the deleted account on your backend — please re-link the installation to my workspace
Project ID: e3380ccb-3be9-4880-8d17-8edf48ac361f
1 Replies
Status changed to Awaiting Railway Response Railway • about 10 hours ago
an hour ago
The service is still authorized under the removed account's GitHub credentials, which is why the GitHub-triggered path fails even though the app is reinstalled. Reconnecting GitHub at the account level doesn't update the per-service authorization.
To fix this, disconnect and reconnect the repository at the service level: go to your service's Settings, disconnect the repo source, then reconnect it to the same repo. This re-authorizes the service under your current GitHub account. You can also do this via the CLI with railway service source disconnect followed by railway service source connect. After reconnecting, you may also want to click Add > GitHub Repository > Refresh on the project canvas to clear any cached state.
Status changed to Awaiting User Response Railway • about 1 hour ago