---
title: "Executions"
description: "Workflow execution record table, saving the context and status of a triggered execution."
---

# Executions

Execution plan records are automatically generated when a workflow is triggered and are managed by the executor. They do not need to be created manually. This document is for field description only.

## Field Descriptions

| Field Name | Type | Required | Default | Description |
| --- | --- | --- | --- | --- |
| id | snowflakeId | No (System generated) | - | Primary key ID, generated by the system. |
| workflow | belongsTo | Yes | - | Associated workflow version (`workflows`), foreign key is `workflowId`. |
| key | string | No | - | Version grouping key, typically equal to `workflow.key`. |
| eventKey | string | No (System generated) | - | Unique event key, used for trigger de-duplication (same workflow + eventKey will be ignored), unique at the database level. |
| jobs | hasMany | No | - | Associated node execution records (`jobs`), used for relational queries. |
| context | json | No | - | Trigger context (event data/input parameters), read by nodes during runtime. |
| status | integer | No | - | Execution status, see the enum below. It is `null` in the queue, `0` when execution starts, and a positive/negative value when it ends. |
| dispatched | boolean | No | false | Whether it has been scheduled to start execution; `false` means it is still in the queue or hasn't been picked up by a worker. |
| stack | json | No | - | Trigger stack (array of execution IDs), used for recursive trigger detection, works with `workflows.options.stackLimit`. |
| output | json | No | - | Summary result produced by Output nodes, available for external reading. |
| createdAt | datetime | No (System generated) | - | Creation time. |
| manually | boolean | No | - | Whether it was manually triggered (e.g., `workflows:execute`). |

## Status Enum (status)

- `null`: QUEUEING (Triggered but still in the queue. This status value is active; use the `dispatched` field to check if execution has started).
- `0`: STARTED (Executing, possibly waiting for async callbacks).
- `1`: RESOLVED (Successfully completed).
- `-1`: FAILED (Node configuration not met/Condition failure).
- `-2`: ERROR (Runtime error).
- `-3`: ABORTED (Process aborted).
- `-4`: CANCELED (Manually canceled while waiting).
- `-5`: REJECTED (Rejected by a manual node).
- `-6`: RETRY_NEEDED (Failed but requires retry).

## Example Values

```ts
const values = {
  workflowId: 10001,
  key: 'wf_group_abc',
  eventKey: 'users:update:12345',
  context: { data: { id: 12345, email: 'a@b.com' } },
  status: null,
  dispatched: false,
  stack: [90001, 90002],
  manually: true,
  output: { result: 'ok' },
};
```