Workflows
Save, activate, pause, and change workflows
Move a validated workflow into Active status and make controlled operational changes.
Automation buildersAdministratorsBeginnerAvailable
What this guide covers
- Active status allows configured trigger events to start new executions.
- Prerequisites: All blocking validation issues fixed.
- Result: Status is Active and a matching real event starts the expected execution.
- Limit: There is no exposed staged rollout or percentage-based deployment control; use Duplicate and A/B Split only for supported workflow behavior.
What this is and when to use it
Active status allows configured trigger events to start new executions.
| Use it when | Expected outcome |
|---|---|
You are ready to put a tested workflow into operation. | Status is Active and a matching real event starts the expected execution. |
You need to stop new executions while editing. | Status is Active and a matching real event starts the expected execution. |
Before you begin
- All blocking validation issues fixed.
- Required numbers, templates, functions, and connected accounts available.
- Sufficient account entitlement and Balance.
Prerequisites
All blocking validation issues fixed. Required numbers, templates, functions, and connected accounts available. Sufficient account entitlement and Balance.
Complete the task
- Save and run tests for every important branch.
- Confirm recipients, sender overrides, external actions, and costs.
- Turn Active on.
- Monitor the first real executions.
- Pause before making changes that could alter live behavior, then retest and reactivate.
Confirm it worked
- Status is Active and a matching real event starts the expected execution.
Common problems
| Symptom | What to check |
|---|---|
Active toggle returns to off | Resolve validation or publish errors and retry. |
Old behavior continues | Confirm the latest edit shows Saved before relying on it. |
Current limitations
There is no exposed staged rollout or percentage-based deployment control; use Duplicate and A/B Split only for supported workflow behavior.
Product boundary
There is no exposed staged rollout or percentage-based deployment control; use Duplicate and A/B Split only for supported workflow behavior.
Where to go next
Related documentation
Workflow lifecycleManage draft, active, paused, and archived workflows, including duplicate and delete actions.Test a workflowRun a saved workflow with test contact and trigger data while preventing message, database, and external side effects.Account and Agent analyticsRead execution totals, success rate, workflow cost, active workflows, node types, failing nodes, and workflow performance.