2 months ago
I'm experiencing an issue where the "Wait for CI" setting in my service configuration resets to OFF after clicking the Redeploy button, even though the setting was previously enabled.
Service Details:
- Service: webmediaform
- Repository: VikaFoer/webmediaform
- Branch: main
- Environment: production
Setup:
- GitHub Actions CI workflow exists at
.github/workflows/ci.yml - Workflow runs successfully on every push to main (green checks on GitHub)
- Service is properly connected to GitHub repo
Issue:
- I enable "Wait for CI" in the service settings via the Railway dashboard
- The setting persists across page refreshes
- After clicking "Redeploy" on an existing deployment, the "Wait for CI" toggle automatically flips back to OFF
- This happens consistently, regardless of whether the CI workflow has completed
Expected Behavior: Once "Wait for CI" is enabled, it should remain enabled for the service and not reset when using the Redeploy button.
Actual Behavior: The Redeploy action appears to restore a previous deployment config snapshot where "Wait for CI" was OFF, causing the UI setting to reset.
What I've Tried:
- Verified GitHub Actions runs and succeeds on main
- Verified the service is connected to the correct GitHub repo and branch
- Reconnected the GitHub source (Disconnect/Connect)
- Checked GitHub app installation permissions
- Confirmed no branch protection rules are enabled in GitHub
- Attempted to set
waitForCIinrailway.toml(not supported)
Question: Is this expected behavior (Redeploy uses a frozen config snapshot), or is this a bug? If expected, can "Wait for CI" be added as a configurable option in railway.toml so it persists across deployments?
3 Replies
2 months ago
We can confirm your webmediaform service is running fine in production. The behavior you're seeing is expected: Redeploy creates a new deployment using the exact same code and configuration snapshot from the original deployment, so it restores whatever settings (including "Wait for CI") were in effect at that time. "Wait for CI" is not currently supported in railway.toml. To deploy with your current service settings respected, use the Command Palette (CMD/Ctrl + K -> "Deploy Latest Commit") instead of Redeploy, as documented here. If you'd like "Wait for CI" to be configurable in railway.toml or persist through Redeploy, you can submit that as a feature request on our feedback board.
Status changed to Awaiting User Response Railway • about 2 months ago
Railway
We can confirm your webmediaform service is running fine in production. The behavior you're seeing is expected: Redeploy creates a new deployment using the exact same code and configuration snapshot from the original deployment, so it restores whatever settings (including "Wait for CI") were in effect at that time. "Wait for CI" is not currently supported in `railway.toml`. To deploy with your current service settings respected, use the Command Palette (`CMD/Ctrl + K` -> "Deploy Latest Commit") instead of Redeploy, as documented [here](https://docs.railway.com/deployments/deployment-actions#redeploy). If you'd like "Wait for CI" to be configurable in `railway.toml` or persist through Redeploy, you can submit that as a feature request on our [feedback board](https://feedback.railway.com).
2 months ago
But I’m still unable to get GitHub updates to deploy automatically to Railway as expected. How exactly should this be configured to work seamlessly?
Also, why does the UI prompt me to redeploy these changes if the "Redeploy" button ignores current service settings? It’s confusing that the most visible action in the dashboard essentially reverts my "Wait for CI" configuration to an older snapshot.
Could you clarify the recommended workflow to ensure that every new push from GitHub respects my dashboard settings without manual intervention?
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Pushes to your connected branch already trigger automatic deployments that respect your current service settings, including "Wait for CI." You don't need to click Redeploy for new commits. The Redeploy button is specifically for re-running a past deployment with its original snapshot, which is why it restores old settings. For your normal workflow, just push to main and the auto-deploy will pick it up with "Wait for CI" honored. If auto-deploys aren't triggering on push, make sure the Railway GitHub App has access to your repo at https://github.com/settings/installations and that the correct trigger branch is set in your service settings.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 • about 1 month ago