2 months ago
Railway's "Wait for CI" feature is not deploying after GitHub Actions complete successfully, even though both GitHub and Railway show the CI checks as passed.
When "Wait for CI" is enabled, Railway should automatically deploy after all GitHub Actions workflows complete successfully.
Railway shows "waiting for CI" status
GitHub Actions workflow runs and completes successfully
Railway dashboard shows CI checks as passed
Railway skips the deployment instead of proceeding
Manual deployment via railway up, the CLI command, works just fine
Deployment ID: b8dc1f54
Status: Skipped
Date: Oct 2, 2025, 1:47 AM
Trigger: Merge pull request #145 from Fliktem/fix/cursor-pointer
Commit: "fix: add missing cursor-pointers"
Source: GitHub (main branch)
Build Logs: No build logs were found for this deployment
This deployment was triggered by a GitHub merge but was skipped despite successful CI completion.
Repository: JBChangelogs/JailbreakChangelogs
Branch: main
Railway Service: Connected to production environment
GitHub Integration: Connected 4 months ago with proper permissions
Please investigate why Railway is not proceeding with deployments for both PR's and normal pushes to the branch.
8 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
2 months ago
Heya, can you confirm the railway github app has all the required permissions?
See https://docs.railway.com/guides/github-autodeploys#enabling-wait-for-ci
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Hello. Yes, I can confirm I have followed those steps. It has been fine for some time now, the issue started today.
I also just tried changing 1 tiny thing in the repo and pushing again and the deployment got skipped yet again. The workflow(s) are not failing either.
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Just did ctrl + k to deploy latest commit manually as I wait for a response. Saying this so that the staff don't see latest one was successful and my issue is solved. I had to do this so the website gets updated.
Attachments
2 months ago
Heya, there's a check suite connected to your repo that's failing. Could you double check connected apps?
Link for the deploy you sent: https://api.github.com/repos/JBChangelogs/JailbreakChangelogs/check-suites/47315952544
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
Oh gosh, terribly sorry
Hadn't seen that
Also just saw it from https://github.com/JBChangelogs/JailbreakChangelogs/actions
I was relying on the main repo age and never saw X's so it seemed everything was passing
Attachments
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved brody • about 2 months ago