Database Reference
Workflow keeps the editable definition, its published versions and each execution separate. A running process therefore remains tied to the version that started it, even when a newer workflow is published later.
| Relationship | Why it matters |
|---|---|
workflow_version belongs to one workflow_definition |
Preserves published workflow revisions under one business definition. |
workflow_run belongs to one workflow_version |
Makes each execution reproducible against the version it started with. |
workflow_run_node belongs to one workflow_run |
Records progress and outcomes for the nodes in an execution. |
workflow_task belongs to one workflow_run |
Connects approvals and other manual decisions to the workflow that created them. |
workflow_audit_log references an entity type and reference |
Records who changed or decided what — definitions, runs and tasks (action, actor, metadata, timestamp). |
workflow_trigger_registry maps an event name to a workflow code |
Keeps the link between a Magento event and the subscribed workflow, optionally limited to store IDs. |
Graph payloads, runtime context and internal execution fields are not part of this reference. Use the workflow services and Admin UI to preserve versioning and state transitions.