Workflows and runs

A workflow is the versioned definition: nodes, edges, triggers, and settings. A run is one concrete pass of that definition at a point in time, with status and logs.

💡 Definition vs execution

	Workflow	Run
Nature	JSON model + Dolibarr metadata	Execution instance
Lifecycle	Draft → active → archived	queued → running → terminal
Storage	Internal llx_knot_* tables	Executions history
Idempotency	Keys on nodes	Applied on each retry

💡 Workflow lifecycle

• Draft: free editing; Simulate allowed when Problems is clean.
• Active: triggers (cron, webhook, object event) can create runs.
• Archived: no new runs; history kept.

💡 Run states

Status	Meaning
queued	Waiting for Knot cron or execution slot
running	Engine processing the node chain
success	Finished without blocking error
error	Failure — check per-node logs
cancelled	Manual cancel
skipped	Branch not taken (e.g. If/Else)

Retry

After a transient failure, retry re-runs the run and can honor idempotency when configured on the node.

💡 See also

• Triggers and scheduling
• Track runs (detailed guide coming soon)