You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/docs/references/automation/execution.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,7 +155,7 @@ const result = CheckpointSchema.parse(data);
155
155
|**acted**|`integer`| ✅ | Total records written / effects dispatched by the run |
156
156
|**skipped**|`integer`| ✅ | Total node executions a closed gate prevented |
157
157
|**unmeasured**|`integer`| optional | Total executions that may have caused an effect the platform cannot count. Absent = not tracked (an older run), which is not the same as zero. |
158
-
|**failed**|`integer`| optional | Total node executions that failed — a fold of `nodes[].failures`, INCLUDING what a delegating node (`subflow` / `map`) rolled up from a child run that completed while containing failures, the way `acted` includes the child's writes: this total answers "what did this run cause", subflows included, so a parent whose child lost rows does not read `failed: 0`. On a run that completed every one of them was contained (caught by a `try_catch` or routed down a `fault` edge) and the run went on. Absent = not tracked (an older run), which is not the same as zero. |
158
+
|**failed**|`integer`| optional | Total node executions that failed — a fold of `nodes[].failures`, INCLUDING what a delegating node (`subflow` / `map`) rolled up from a child run that COMPLETED while containing failures: this total answers "what did this run cause", subflows included, so a parent whose child lost rows does not read `failed: 0`. A child that FAILED — whether or not it also contained failures before it failed — counts once, as the delegating step's own failure, and its own `failed` stays on its row (unlike `acted`, which carries a failed child's writes). On a run that completed every one of them was contained (caught by a `try_catch` or routed down a `fault` edge) and the run went on. Absent = not tracked (an older run), which is not the same as zero. |
|**gates**|`{ nodeId: string; targetNodeId: string; edgeId?: string; label?: string; … }[]`| ✅ | Gates that closed during the run, most-skipped first |
161
161
|**detailOmitted**|`boolean`| optional | Set when persistence dropped `nodes`/`gates` to keep the stored row bounded — the totals are still exact. Declared so empty arrays are never mistaken for "nothing ran". |
@@ -219,7 +219,7 @@ const result = CheckpointSchema.parse(data);
219
219
|**selected**|`integer`| optional | Records this node READ or matched (a `get_record` query, a lookup) |
220
220
|**acted**|`integer`| optional | Records this node WROTE (created / updated / deleted) or effects it dispatched (notifications delivered) |
221
221
|**unmeasuredEffect**|`boolean`| optional | This execution may have caused an effect the platform cannot count (an external write through a connector). NOT interchangeable with `acted: 0` — it says the count is unknown, not that it is zero. |
222
-
|**failures**|`integer`| optional | Node executions that failed inside a child run this execution delegated to and went on from — a `subflow` child or a `map` item whose run COMPLETED while containing failures: its `summary.failed`, rolled up so the parent answers "what did this run cause" the way `acted` already does. Folds into this node's `failures` and so into the run-level `failed`. NOT this execution's own outcome: a step that failed is `status: 'failure'` and counts once through `nodes[].failures`, and a child that FAILED rather than contained is exactly that step failure — its own `failed`stays on the child's run row and nothing rides up here. Absent = delegated nothing, or the child tracked no count; not zero. |
222
+
|**failures**|`integer`| optional | Node executions that failed inside a child run this execution delegated to and went on from — a `subflow` child or a `map` item whose run COMPLETED while containing failures: its `summary.failed`, rolled up so the parent answers "what did this run cause". Folds into this node's `failures` and so into the run-level `failed`. NOT this execution's own outcome: a step that failed is `status: 'failure'` and counts once through `nodes[].failures`, and a child that FAILED — whether or not it also contained failures before it failed — is exactly that step failure: its own `failed`, contained and fatal alike, stays on the child's run row and nothing rides up here (unlike `acted`, which does carry a failed child's writes). Absent = delegated nothing, or the child tracked no count, or the producer did not track it; never zero. |
223
223
224
224
### Nested Shape: `ExecutionStepLog.skippedBy`
225
225
@@ -241,7 +241,7 @@ const result = CheckpointSchema.parse(data);
241
241
|**selected**|`integer`| optional | Records this node READ or matched (a `get_record` query, a lookup) |
242
242
|**acted**|`integer`| optional | Records this node WROTE (created / updated / deleted) or effects it dispatched (notifications delivered) |
243
243
|**unmeasuredEffect**|`boolean`| optional | This execution may have caused an effect the platform cannot count (an external write through a connector). NOT interchangeable with `acted: 0` — it says the count is unknown, not that it is zero. |
244
-
|**failures**|`integer`| optional | Node executions that failed inside a child run this execution delegated to and went on from — a `subflow` child or a `map` item whose run COMPLETED while containing failures: its `summary.failed`, rolled up so the parent answers "what did this run cause" the way `acted` already does. Folds into this node's `failures` and so into the run-level `failed`. NOT this execution's own outcome: a step that failed is `status: 'failure'` and counts once through `nodes[].failures`, and a child that FAILED rather than contained is exactly that step failure — its own `failed`stays on the child's run row and nothing rides up here. Absent = delegated nothing, or the child tracked no count; not zero. |
244
+
|**failures**|`integer`| optional | Node executions that failed inside a child run this execution delegated to and went on from — a `subflow` child or a `map` item whose run COMPLETED while containing failures: its `summary.failed`, rolled up so the parent answers "what did this run cause". Folds into this node's `failures` and so into the run-level `failed`. NOT this execution's own outcome: a step that failed is `status: 'failure'` and counts once through `nodes[].failures`, and a child that FAILED — whether or not it also contained failures before it failed — is exactly that step failure: its own `failed`, contained and fatal alike, stays on the child's run row and nothing rides up here (unlike `acted`, which does carry a failed child's writes). Absent = delegated nothing, or the child tracked no count, or the producer did not track it; never zero. |
245
245
246
246
247
247
---
@@ -285,7 +285,7 @@ const result = CheckpointSchema.parse(data);
|**status**|`Enum<'success' \| 'failure' \| 'skipped'>`| ✅ | Terminal status of the node across the run — `failure` if any execution failed, else `success` if any succeeded, else `skipped`. Judged on this node's OWN executions: a delegating node (`subflow` / `map`) whose child completed while containing failures reads `success` here with `failures > 0`|
287
287
|**runs**|`integer`| ✅ | Times the node executed (loop iterations and parallel branches each count) |
288
-
|**failures**|`integer`| ✅ | Executions that failed — a failure a `try_catch` caught or a `fault` edge routed counts here too — plus what a delegating execution rolled up from its child run (`metrics.failures`: the contained failures of a `subflow` child or a `map` itemthat completed), the way `acted`carries the child's writes; the run-level `failed` is the sum of this across `nodes`|
288
+
|**failures**|`integer`| ✅ | Executions that failed — a failure a `try_catch` caught or a `fault` edge routed counts here too — plus what a delegating execution rolled up from a child run that COMPLETED (`metrics.failures`: the contained failures of a `subflow` child or a `map` item). On a delegating node this may therefore exceed `runs` and is no longer only this node's own failed executions; a child that FAILED adds only the step's own failure (unlike `acted`, which carries a failed child's writes too); the run-level `failed` is the sum of this across `nodes`|
289
289
|**skipped**|`integer`| ✅ | Times a closed gate kept this node from running at all |
290
290
|**selected**|`integer`| optional | Records read across every execution — omitted for a node that reads none |
291
291
|**acted**|`integer`| optional | Records written / effects dispatched across every execution — omitted for a node that writes none |
@@ -304,7 +304,7 @@ const result = CheckpointSchema.parse(data);
304
304
|**acted**|`integer`| ✅ | Total records written / effects dispatched by the run |
305
305
|**skipped**|`integer`| ✅ | Total node executions a closed gate prevented |
306
306
|**unmeasured**|`integer`| optional | Total executions that may have caused an effect the platform cannot count. Absent = not tracked (an older run), which is not the same as zero. |
307
-
|**failed**|`integer`| optional | Total node executions that failed — a fold of `nodes[].failures`, INCLUDING what a delegating node (`subflow` / `map`) rolled up from a child run that completed while containing failures, the way `acted` includes the child's writes: this total answers "what did this run cause", subflows included, so a parent whose child lost rows does not read `failed: 0`. On a run that completed every one of them was contained (caught by a `try_catch` or routed down a `fault` edge) and the run went on. Absent = not tracked (an older run), which is not the same as zero. |
307
+
|**failed**|`integer`| optional | Total node executions that failed — a fold of `nodes[].failures`, INCLUDING what a delegating node (`subflow` / `map`) rolled up from a child run that COMPLETED while containing failures: this total answers "what did this run cause", subflows included, so a parent whose child lost rows does not read `failed: 0`. A child that FAILED — whether or not it also contained failures before it failed — counts once, as the delegating step's own failure, and its own `failed` stays on its row (unlike `acted`, which carries a failed child's writes). On a run that completed every one of them was contained (caught by a `try_catch` or routed down a `fault` edge) and the run went on. Absent = not tracked (an older run), which is not the same as zero. |
|**gates**|`{ nodeId: string; targetNodeId: string; edgeId?: string; label?: string; … }[]`| ✅ | Gates that closed during the run, most-skipped first |
310
310
|**detailOmitted**|`boolean`| optional | Set when persistence dropped `nodes`/`gates` to keep the stored row bounded — the totals are still exact. Declared so empty arrays are never mistaken for "nothing ran". |
@@ -318,7 +318,7 @@ const result = CheckpointSchema.parse(data);
|**status**|`Enum<'success' \| 'failure' \| 'skipped'>`| ✅ | Terminal status of the node across the run — `failure` if any execution failed, else `success` if any succeeded, else `skipped`. Judged on this node's OWN executions: a delegating node (`subflow` / `map`) whose child completed while containing failures reads `success` here with `failures > 0`|
320
320
|**runs**|`integer`| ✅ | Times the node executed (loop iterations and parallel branches each count) |
321
-
|**failures**|`integer`| ✅ | Executions that failed — a failure a `try_catch` caught or a `fault` edge routed counts here too — plus what a delegating execution rolled up from its child run (`metrics.failures`: the contained failures of a `subflow` child or a `map` itemthat completed), the way `acted`carries the child's writes; the run-level `failed` is the sum of this across `nodes`|
321
+
|**failures**|`integer`| ✅ | Executions that failed — a failure a `try_catch` caught or a `fault` edge routed counts here too — plus what a delegating execution rolled up from a child run that COMPLETED (`metrics.failures`: the contained failures of a `subflow` child or a `map` item). On a delegating node this may therefore exceed `runs` and is no longer only this node's own failed executions; a child that FAILED adds only the step's own failure (unlike `acted`, which carries a failed child's writes too); the run-level `failed` is the sum of this across `nodes`|
322
322
|**skipped**|`integer`| ✅ | Times a closed gate kept this node from running at all |
323
323
|**selected**|`integer`| optional | Records read across every execution — omitted for a node that reads none |
324
324
|**acted**|`integer`| optional | Records written / effects dispatched across every execution — omitted for a node that writes none |
0 commit comments