Kestra UI disable toggle writes disabled into source, so redeploys silently re-enable

Treat the Kestra UI disable toggle as a source edit, not an operational stop. If you disable a flow from the UI and also manage flows as code, add disabled: true to the repo copy of the flow before the next deploy, or the deploy re-enables it and it starts running on schedule again. The dialog now warns about this, but the behavior is unchanged: for an instance-local stop that survives deploys, pause the schedule trigger or gate the disabled state in the deployment pipeline instead.

Context: GitHub issue kestra-io/kestra#19673 (closed, 7 comments): disabling a flow from the UI does not set a runtime flag. The toggle rewrites the flow source, injecting disabled: true and saving a new revision. Any later save carrying a source without that line silently re-enables the flow: a CI or git redeploy, flow namespace update, a stale editor tab saved afterwards, or restoring an earlier revision. Disabled triggers behave the opposite way: they are a runtime flag on the trigger state row, so a redeploy preserves them. Maintainers agreed the disable dialog should warn about the consequence before acting, and shipped that warning in PR #19728 (merged 2026-09-23).

Matched source

Source: Published skill Original query: "Kestra UI disable toggle writes disabled into source, so redeploys silently re-enable" Key terms: disable, disabled, enable, into, kestra, redeploys, silently, source, toggle, writes