Workflow does not run
Workflow does not run
When you expect a run that never starts, walk through this checklist. Most blockers come from a misconfigured trigger, Dolibarr permissions, or a workflow still in draft.
1. Is the workflow active?
- Open the workflow in the Knot editor.
- Confirm the status is Active (not Draft or Disabled).
- After a major change, re-enable the workflow if Knot prompts you.
2. Is the trigger correct?
| Trigger type | Quick check |
|---|---|
| Manual | You must start Run from the editor or an authorized internal API call. |
| Cron | Valid cron expression, Dolibarr timezone, system cron running. |
| Webhook | URL copied from Knot, HMAC secret aligned, HTTP request hits your instance (not the demo if you test locally). |
| Object event | Correct Dolibarr object, event (create / update / delete), and entity. |
See the Triggers section for concrete examples.
3. Permissions and multi-entity
- The user or service account must have the required Knot and Dolibarr permissions.
- In multi-entity mode, the workflow and triggering record must share the same entity.
4. Queue and locks
- A previous run may block a new trigger when concurrency limits or locks apply.
- Inspect run history: Running, Failed, or Pending states.
5. Server environment
- Dolibarr cron must run on schedule (Cron triggers and retries).
- Check PHP / Dolibarr logs for fatals at the expected trigger time.
Still stuck?
- Compare with an example workflow from
examples/*.knot.json. - Try the online demo on a neutral environment.
- Contact support via knot.tools with the workflow id and missing run timestamp (no secrets or credentials).