AutomationHistory
One execution run of an Automation, from the trigger firing to
completion, failure, or waiting.
status waiting means the run is paused mid-flow (e.g. on a delay or
input step) and will resume automatically at resumeAt / nextNodeNs.
AutomationHistoryFields
Unique execution history document id.
Execution engine's run id — stable across waiting/resume cycles for the same run.
Namespace of the automation that ran.
Namespace of the trigger that started this run.
Trigger type at the time this run started.
Trigger event at the time this run started.
Id of the entity the run acted on (typically a customer/conversation).
Type of targetId (e.g. customer).
Run status: running, completed, failed, waiting, or archived.
When the run started.
When the run finished, if it has.
Total run duration in milliseconds, once completed.
Node the run is paused at, when status is waiting.
Why the run is paused (e.g. delay, awaitingInput).
When a waiting run is scheduled to resume, if time-based.
Number of nodes executed so far in this run.
Failure detail, when status is failed.
Last time this history document changed.
Parent run's executionId, when this run was spawned by another (e.g. a sub-flow).
Per-node execution trace — see ExecutionStep. Populated in full on AutomationHistoryDetail.
Target customer's phone, denormalized for display.
Target customer's name, denormalized for display.