Activate a workflow
An inactive workflow is a frozen definition: no trigger starts it. Activation arms triggers and allows automatic runs.
🔁 Before you activate
Quick checklist:
- Simulate passes on happy path and one error path.
- Credentials and SMTP tested.
- Dolibarr rights OK for the execution account: Permissions.
- Trigger configured (Cron, webhook, object event, or manual only).
🔁 Activate
- Open the workflow → Settings tab or Active toggle.
- Choose the primary trigger if several exist.
- Save. State becomes Active; runtime stores
next_run_atfor Cron.
🔁 Runtime state
| State | Meaning |
|---|---|
| Draft | Free editing, no auto run |
| Active | Triggers armed |
| Paused | Definition kept, auto runs suspended |
| Disabled | Like pause; ops alert possible |
Deactivation keeps run history: you can re-enable without losing logs.
🔁 Deactivate cleanly
- Set the workflow to Paused or Disabled.
- Wait for in-flight runs to finish (cron queue).
- Edit the graph if needed, Simulate again, then reactivate.
During major Dolibarr maintenance, disable affected Knot workflows first.
🔁 Triggers to verify on activation
| Type | Check |
|---|---|
| Cron | Server timezone, valid expression — Cron |
| Webhook | Rotated secret, TLS — Webhook |
| Object event | Correct object and create/update/delete — Object event |