"Wait for CI" not triggering deployments after GitHub Actions pass
maingocanh1702
HOBBYOP

a month ago

Issue:

"Wait for CI" is enabled on my web service. GitHub Actions CI completes successfully, but Railway never picks up the check_suite completion event — no deployment is triggered.

What I've tried:

1. Pushed multiple commits to main — all pass CI on GitHub Actions (quality + e2e jobs), but Railway shows no new deployments

2. Disconnected and reconnected the GitHub repo on Railway

3. Re-authorized the Railway GitHub App (confirmed "All repositories" access with full permissions: actions, checks, code, deployments, etc.)

4. Toggled "Wait for CI" off and back on

5. Using Cmd+K → "Deploy latest commit" works fine — only automatic webhook-based deploys are broken

What works:

- Manual deploy via command palette (Cmd+K → Deploy latest commit)

- Auto-deploy works when "Wait for CI" is OFF

- GitHub Actions CI passes consistently

What doesn't work:

- Auto-deploy with "Wait for CI" ON — Railway never receives or processes the check_suite completed webhook from GitHub

Expected: After GitHub Actions CI passes, Railway should automatically trigger a deployment.

Has anyone encountered this problem, and if so, how did you solve it?

0 Replies

Welcome!

Sign in to your Railway account to join the conversation.

Loading...