Run History & Debugging
Trace every automation run node-by-node: inputs, outputs, status, errors, and duration.
Overview
Every time an automation fires, Pomavo records a run. A run captures which trigger started it, which nodes executed, what each node received and produced, and how long everything took. This makes automations fully auditable and easy to debug.
Anatomy of a Run
Each run contains a node run for every node the engine touched. A node run records:
- Status: succeeded, failed, or skipped
- Inputs: the resolved values delivered to each input port
- Outputs: the values the node emitted on each output port
- Duration: how long the node took
- Error: the message, if the node failed
Inputs and outputs are stored as structured data, so you can expand any node and see the exact object that flowed across each edge, including nested ticket, user, and link objects.
Why a Node Was Skipped
Nodes are skipped, not failed, when their branch is not active. Common reasons:
- The node belongs to a trigger branch that did not fire in a multi-trigger automation.
- An upstream condition evaluated false, so the downstream branch was gated off.
- Every input the node needs came from a skipped source, leaving it with nothing live to run on.
Skipped nodes are expected and do not indicate an error.
Output Contract Validation
The engine validates each node's output against its declared shape before passing it downstream. If a node emits the wrong shape - for example, a raw ID where a full object is expected - the run records a clear contract violation that names the node, the port, and the expected versus actual type. This catches the most common class of automation bug at its source instead of letting a silent null propagate.
Debugging Tips
Start at the trigger
Confirm the run was started by the trigger you expected and that its outputs carry the right ticket.
Follow the active path
Walk node-by-node down the branch that ran. Look for the first node whose output is empty or unexpected.
Use Inspect nodes
Drop a Debug → Inspect node onto an edge to capture exactly what value crosses it, then re-run and read it back in the run history.
Check skips and conditions
If a branch did not run, find the condition or trigger gate that skipped it.
Administering Runs
Platform administrators can inspect the underlying background jobs, including automation evaluations and scheduler resumes, from the Admin Dashboard, with full per-job logs and status.