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, and watch events.

Filter by status (All / Success / Info / Skipped / Failed), by step type, or search. **Dev Console** is the verbose text log.

History stays in `chrome.storage.local` on this computer. Activity keeps the last 20 sessions per automation, with at most 500 events and 200 target rows in each session. Older detail in a long session is trimmed and counted. Dev Console keeps the last 300 entries per automation.

You can export Targets CSV, Events CSV, or JSON, and Clear 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.

## Not this control

Is not a graph step. Is not Dev Console (that is the verbose log in the same drawer). Is not a cloud audit.

## Related guides

The [side panel tour](/blog/welcome) shows where to open Activity. The [guide to walking through links](/blog/walk-through-links-in-chrome) explains the kind of multi-URL run where Activity helps diagnose a missed selector.