I should also mention, I have all the latest requested github permissions approved.

I am experiencing the exact same issue. Everything was working perfectly until about two days ago, and suddenly Railway started ignoring the CI status.

Current Behavior:

• "Wait for CI" is Enabled in Railway settings.

• When I push code, Railway triggers a deployment immediately, completely ignoring the GitHub Action status (even while it is still "Pending" or if it eventually fails).

Troubleshooting steps I've already taken (none worked):

1. Toggled the "Wait for CI" setting Off and On multiple times.

2. Verified that the GitHub Check name matches exactly.

3. Renamed the workflow file (from ci.yml to test.yml) and the Job ID to force a cache reset.

4. Confirmed that GitHub Actions are indeed running and reporting status on the commit.

5. Attempted to disconnect and reconnect the repository.

It seems like Railway is simply not listening to the check status webhooks anymore for this repo. Is there a known fix or is this a regression on your end?

+1 same problem

I am just not sure whether I applied the newest github permission, how can I do that?

If you go into your github repo or organisation settings, then go under integrations, when you configure the Railway app, there should be a section near the permissions asking you to grant new ones. (If I recall correctly anyway).

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

🛠️ The ticket Deployments proceeding despite failed checks has been marked as triage.

Thanks for the update and for tracking this issue.

While the engineering team looks into it, is there an official way to disable automatic deployments (switch to Manual Mode only) for a connected repo?

Since the CI checks are currently being bypassed, I want to prevent every push from automatically triggering a build, but I couldn't find a specific "Disable Auto-Deploy" toggle in the Service Settings > Git section.

If this setting exists, could you please point me to its exact location?

If not, I strongly suggest adding this feature. It is essential for maintaining control over production environments, especially when CI integrations face issues like this.

Not from Railway team, but what you can do is to disconnect the repo from the Railway service and only if you want to redeploy set the connection back again. Not a pretty solutions, but should work.

Kudos <3

Hi there! We just pushed an update addressing the issue. Can you confirm it’s behaving correctly? Thanks!

Builds appear to now be Waiting for CI before they start building their images, so yep, this appears to be fixed!

That's great! We’ll close this ticket then. Feel free to reopen if you need anything else!