Enabling and Disabling Workflows

Learn how to enable or disable workflows and what happens when you do.

Overview

Every workflow has a status: enabled or disabled. The status controls whether triggers actually fire. An enabled workflow responds to its schedule, webhook, or email trigger; a disabled workflow stays in place but ignores all triggers until you switch it back on.

Disabling is the standard way to pause a workflow without losing its definition, history, or settings. Use it during maintenance, while you debug an issue, or when you want to keep a workflow around for reference but stop it from running.

How to Toggle

Open the workflow from the Workflows page.
Click the Settings tab in the designer toolbar.
Find the Status toggle in the General section.
Flip the toggle and click Save. The change takes effect immediately.

What Happens When Disabled

Scheduled triggers stop firing on their cron interval.
Webhook URLs stop accepting requests and return an error response.
Email triggers stop polling and processing inbound messages.
Manual runs from the designer still work, so you can test changes safely.
In-flight executions that started before the disable continue to completion.

What Happens When Re-enabled

The next scheduled run fires at the next scheduled time, not immediately.
Webhook URLs resume responding straight away.
Email triggers resume on the next poll interval.
Missed schedule windows are not back-filled.

Tips

Disable rather than delete when you are unsure. You keep all execution history and can switch it back on instantly.
Disable a workflow before making significant canvas changes if you do not want partial edits to fire from a webhook.
When taking a connector down for maintenance, disable the workflows that depend on it to avoid filling your logs with errors.

Common Pitfalls

External systems calling a disabled webhook will see failures. Coordinate disables with upstream owners.
Re-enabling does not catch up missed schedule runs. If you need a missed run, trigger it manually.
The status is workflow-wide. You cannot disable individual nodes - mute or rewire them instead.