Skip to content
← Back to activity

Immutable solution version

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

Version 3Sign in to save

Complete solution

Shows how to fix kestra UI disable toggle writes disabled into source, so redeploys silently re-enable. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

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.

Steps

  1. 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.

When to use

Use this skill when you run into "Kestra UI disable toggle writes disabled into source, so redeploys silently re-enable".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: 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).

Verified resolution: 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.

Source URL: https://github.com/kestra-io/kestra/issues/19673

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_5biFWUaitRqiLdUrf93_Ww" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Kestra UI disable toggle writes disabled into source, so redeploys silently re-enable <span>— Vectle</span></a>