Can you make sure you have given the Railway App bot access to your repositories?

GitHub Settings -> Applications -> Railway App -> Configure -> Repository access

Then please go into your Railway account and unlink and relink the GitHub integration.

I did this more than once, and I did it again now (including removing access and giving it back to all repos and reconnecting via account settings), error is still there.

Since you've already tried the standard GitHub reconnection steps multiple times, let's look at this from a different angle. The fact that this suddenly broke yesterday for just one repo while others still work suggests something specific to this repository or service connection.

A few things worth checking: Has anything changed with this specific repository on the GitHub side—like a rename, ownership transfer, or being moved to/from an organization? Also, if this repo belongs to a GitHub organization, sometimes org admins need to re-approve the Railway app after certain permission changes, even if your personal account still has access.

One thing you could try is disconnecting the GitHub repo from this service entirely (not just unlinking your account, but removing the repo connection from the service settings), then reconnecting it fresh. If that still fails, try creating a brand new service in the same project and connecting it to that repository—this would tell us if the issue is with the service itself or the repo connection more broadly.

I have encountered this issue as well, but on a larger scale. It only started this week. I can't deploy from any GitHub repo, to a new or existing service. I also cannot sign into Railway using the "Continue with GitHub" option (there is an error that states "Error authenticating with GitHub, Problem completing OAuth login").

Disconnecting and reconnecting the repo to the service, as well as trying to deploy a new service, results in an error "Cannot setup automatic deploys for YourOrg/YourRepo because no one in the workspace has access to it". However the Railway user is also an owner in the organization repo and has access to all repos.

Given that others are reporting this, I wanted to highlight that this may be a broader issue.

Yep, this is tied to the GitHub ratelimiting issue. Ack there was a problem, we should be out of the woods now but will monitor for any further errors.

This happened to me several times this week, and now again this morning. I cannot deploy into a new PR environment.

Can you create your own thread for this? Would love to help debug there so its all isolated