Logs & Run History
Every rule set run produces a run record and a stream of timestamped log entries, tied together by a correlation id so you can trace exactly what happened.
Runs and logs
Each environment keeps two kinds of records:
- Run — one entry per run, with its status (Pending, Running, then a final state), the rule set and project, who or what started it, timing, and any top-level error.
- Log entry — a single line written during the run. Each entry carries a timestamp, a severity level, the correlation id, and breadcrumb fields identifying where in the rule set it came from.
Log levels
Log entries use standard severity levels:
| Level | Typical use |
|---|---|
| Trace | Very fine-grained diagnostic detail |
| Debug | Developer-oriented detail; hidden unless you opt in |
| Information | Normal run progress (the default view) |
| Warning | Recoverable or unexpected conditions |
| Error | A failed action or rule |
| Critical | A failure that halts the run |
The viewer shows Information and above by default. A debug logs toggle pulls in Trace and Debug entries on demand, so verbose diagnostics never clutter the normal view.
Correlation IDs
A correlation id is created when a run starts and stamped onto the run and every log entry it produces. When one rule set hands off to another — for example through a workflow or a continued run — the work stays grouped under a shared correlation, so a multi-step run reads as a single, ordered story.
Log messages can also reference other correlations. The viewer renders these as clickable links: selecting one opens that correlation's full log, letting you follow a chain across rule sets without losing your place.
Breadcrumbs
Each log entry includes breadcrumb fields that pinpoint its origin within the rule set: the rule set name, the rule, the action set, and the individual action (with its action type). The viewer renders these as a compact trail next to the message, so you can see at a glance which rule and action wrote a given line — and jump straight to the rule set in the editor.
The log viewer
The in-app log viewer lists recent runs newest-first and lets you expand any run to load its log entries inline. From the toolbar you can filter by project, and deep links can pre-select a specific project, correlation, run, or log entry.
- Live updates — while a run is Pending or Running, the viewer refreshes on its own so you can watch progress without reloading.
- Incremental loading — runs and log entries load more on demand, so large histories don't all load at once.
- Attachments — entries that captured files show download links you can click to retrieve them.
- By correlation — a dedicated dialog shows a single correlation's complete log, independent of the run list, and is what inline correlation links open.
Recent logs
A compact “recent logs” panel surfaces the latest handful of runs (with status) for an environment — useful as an at-a-glance health check on a dashboard. Selecting a run takes you into the full viewer for detail.
Start from the failed run, expand it to read its Information-level log, then turn on debug logs if you need Trace/Debug detail. Follow breadcrumbs to the offending rule and action, and click any correlation link to jump into related runs.