a month ago
Hello Railway Support,
I'm experiencing an issue with my MedScholars staging service.
Project: dependable-delight
Environment: staging
Service: medscholar
Repository: medscholar/medscholar
Branch: staging
When I enable Wait for CI and apply the pending change, the setting returns to OFF. The change disappears without persisting, and no new deployment occurs.
I have confirmed that the Railway GitHub App has access to all repositories and the required Actions, checks, deployment, and workflow permissions.
The staging website is also pinned to an older commit, with automatic deployment disabled.
Could you investigate why the Wait for CI setting will not persist and help restore secure, CI-gated deployments from the staging branch?
Our setting reverted after applying a staged configuration change, not after choosing Redeploy on an existing deployment
Thank you.
1 Reply
a month ago
Wait for CI only applies to automatic deployments from a branch. While a service is pinned to a specific commit, applying the change has no branch deployment to attach the setting to, so it doesn't save and the toggle goes back to OFF. Applying that change also doesn't start a deployment on its own, which is why no new deployment appeared.
To get CI-gated deploys from staging, the service first needs to go back to deploying automatically from the staging branch rather than a pinned commit. Once that's done, turn on Wait for CI and apply it again. Pushes to staging will then wait for your GitHub checks to pass before they deploy.
Status changed to Awaiting User Response Railway • about 1 month ago
22 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 22 days ago