Skip to content

Reference & Data Model

Workflow deployment (workflow_deployment)

A workflow deployment is a stored, immutable version of a workflow's rules document.

Every successful save of a workflow creates a new deployment: the validated rules document together with the compiled engine definition, stored immutably. Runs reference the deployment version, not a later state. This keeps it traceable which version produced a run. (Data type: system data)

Not as a page of its own. Visible as the version label „v3“ of an Execution. Polaris names the active version when it reads a workflow (baseVersion).

Field Technical Type Required Meaning Notes
Version version Number yes consecutive per definition (1, 2, 3 …) System
Status status Selection yes active (running), superseded (replaced), proposed (awaiting acceptance) System; not displayed

All further columns (compiled definition, commit hash, creator, timestamp) are relevant server-side only and are displayed nowhere.

Related to Kind Required On delete
Workflow definition belongs to yes deployment deleted along
Trigger has exactly one (via version) yes –
  • The client can only read deployments; the only write sources are the workflow functions (workflow_v3_upsert, workflow_v3_accept).
  • A newly active version starts disabled when it was accepted; a direct save by the owner keeps the enabled state of the previous version.

Workflow definition · Trigger