Runs and captured history

The Runs workspace reads history captured by Core for the current project. Recording continues without an Editor.

Inspect a run

1. Select the automation and run nearest the time of the problem.
2. Follow the execution timeline to locate an error, skipped step or unexpected branch.
3. Select a step occurrence and inspect captured before/after values.
4. Use search, nested paths, changes-only filtering and path copying to inspect runtime, variables, macro inputs, payload and event data.
5. Open the historical structure or compare with a preceding successful run when available.

Repeated macro and loop occurrences remain separate. Historical values and structure are not replaced with today's project or current variables. Source navigation is checked against the current project; an old step address may no longer match.

The nested Set Variable occurrence belongs to Remember the viewer. It remains visible within the captured macro execution.

In this controlled run, the selected step changes the empty string to Welcome completed. The lower viewer displays the selected after-step value.

Retention

History recording is enabled by default, with 100 completed records per automation and a 500 MiB project journal limit. A run has a separate 32 MiB safety limit. Active writes can temporarily exceed the selected project limit.

History settings belong to this project and have their own revision. Disabling recording stops new records while retained history remains readable. Clearing history removes completed/recovered records, not active runs.

Open History storage to review this project's retention controls. This example contains complete records; it does not illustrate an interrupted capture.

Read incomplete data carefully

An interrupted, truncated, dropped or damaged record is marked incomplete. An absent trace is not proof that a step never ran. Values omitted from an older capture cannot be recovered by increasing retention later.

History can contain viewer messages and projected values. Review it before sharing. See Compare runs and Projects for transfer limitations.