2 hours ago
Hello Railway Support,
We need confirmation of current Railway behavior before we change one autodeploy setting.
A production service has one unapplied staged change.
The change deletes an opaque service variable.
We have not applied or discarded the change.
Please confirm what happens when we disable GitHub autodeploy in the current Railway dashboard.
- Does the action apply the existing staged changeset?
- Does it discard or alter the existing staged changeset?
- Does it combine the autodeploy change with the staged changeset?
- Can it start a build, restart, redeployment, or deployment?
- Does the behavior differ when the staged change belongs to the same service?
- Does the behavior differ when the staged change belongs to another service in the same Railway environment?
- Does the autodeploy change apply immediately, or does it become another staged change?
- Is there an API or GraphQL operation that changes only the autodeploy setting?
- Can the staged deletion remain unchanged and unapplied after autodeploy is disabled?
Please confirm that your answer applies to the current Railway dashboard and production environment model.
Please state any plan, interface, or service-relationship condition that changes the answer.
We do not authorize a deployment or staged-change application as part of this support request.
Please provide information only.
Do not change settings, edit or discard staged changes, or start operational actions.
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 hours ago
2 hours ago
Staged changes in an environment are applied only when someone commits them with Deploy, and that commit applies the whole environment changeset, not just the service you are viewing. Discard Changes likewise discards the entire changeset, and there is no per-change discard. So your staged variable deletion stays unapplied until someone commits or discards that changeset, whether it belongs to the same service or another service in the environment.
Disabling autodeploy stops new commits on the connected branch from deploying automatically. Manual deploys remain available through Deploy Latest Commit in the Command Palette.
We have not verified whether the autodeploy toggle applies immediately or is added to the pending changeset next to your deletion, and we have not verified a public API operation that changes only that setting. Before and after toggling, you can check the environment's pending changes in the dashboard or with the public environmentStagedChanges query. If the autodeploy change appears there alongside the deletion, committing would apply both together, since a commit takes the full changeset. If you ever do commit staged changes, Alt+Shift+Enter commits them without triggering deploys, but that still applies the variable deletion.
None of the behavior above depends on your plan.
Status changed to Awaiting User Response Railway • about 2 hours ago