Use Activity to trace a run and find where a step skipped work or failed. Every automation card has Activity. One local session starts at Start or Restart and records each block outcome plus run, collect, target, cycle, watch, and alert events. Webhook deliveries show a redacted result per destination (accepted, rejected, or timed out) — never the full URL or request body.
Filter by status (All / Success / Info / Skipped / Failed), by step type, or search. Dev Console is the verbose text log.
History stays in the local Results database until explicitly deleted. The side panel shows the latest 20 sessions with a bounded view of events and target rows. Use View results in Activity, or Dashboard in the panel header, to open retained runs, per-link activity, diagnostic logs, files, and datasets. Rerunning or removing an automation preserves its retained history.
Use Targets CSV, Events CSV, or JSON to export the log. Clear History removes recorded history.
How to open it
On the automation card, click Activity. The drawer updates while a run is going. Pause and Restart abort the current wait or step; the session still records what already happened.
Limits and related controls
Activity is the run log, rather than a graph step. Its Dev Console view adds diagnostic detail. Use the Dashboard to browse retained history and files; neither view syncs history to the cloud.
Related guides
The side panel tour shows where to open Activity. The guide to walking through links explains the kind of multi-URL run where Activity helps diagnose a missed selector.
See the Dashboard guide for browsing retained results, exports, and local storage.