Cron trigger

A Cron trigger starts the workflow on a schedule. Dolibarr must run the system cron so Knot can compute next_run_at and enqueue runs.

⚡ Prerequisites

OS cron or Plesk task calling htdocs/cron/cron_run.php (or equivalent) regularly.
Workflow in Active state.
Execution account with required rights: Permissions.

Knot editor with a Cron trigger scheduled at 08:00 — Click to enlarge

⚡ Syntax

Knot accepts standard 5-field cron expressions:

┌───────────── minute (0 - 59)
│ ┌───────────── hour (0 - 23)
│ │ ┌───────────── day of month (1 - 31)
│ │ │ ┌───────────── month (1 - 12)
│ │ │ │ ┌───────────── day of week (0 - 6) (Sunday = 0)
│ │ │ │ │
* * * * *

⚡ Examples

Expression	Effect
`0 8 * * *`	Every day at 08:00
`0 * * * *`	Every hour at :00
`/15 * * *`	Every 15 minutes
`0 9 * * 1-5`	Weekdays at 09:00

Match frequency to business volume: an aggressive Cron multiplies runs and DB load.

⚡ Timezone

The PHP server uses OS or php.ini timezone. DST shifts can move sends by one hour.

Verify date.timezone on hosting.
For “9 AM Paris time”, document server TZ in your internal runbook.

⚡ Gotchas

Late Dolibarr cron → late Knot runs (queue backlog).
Two workflows on the same slot → CPU spike; stagger minutes.
No default idempotency: if a run lasts longer than the interval, overlaps are possible — use Logic or business locks.