Zap history, run statuses and tasks

Zap history is the logbook of your automations. Every run is listed with its time, its Zap and its status. Open a run to see each step's input data (what went in) and output data (what came back).

Common statuses:

• Success: every step that should run did run.
• Filtered: a filter step stopped the run on purpose (covered in the filters lesson). Nothing is wrong.
• Errored: a step failed, for example the app rejected the data.
• Held, Waiting or Delayed: the run is paused, for example by a Delay step or while waiting for an approval.
• Stopped or halted: the run ended early, for example because a step had nothing to do.

You can filter history by date, Zap, app, folder, owner and status, and search it. You can also open runs from inside the Zap editor while you build.

The history page also shows task usage. Most successful action steps use one task; some steps use more, such as Code steps with a longer runtime or AI steps with tools. Filters and paths themselves use none.

Unsuccessful runs can be replayed (run again), which the error-handling lesson covers.

History is not an archive: Zapier only guarantees about 60 days of run data. If you need long-term records, for example for an audit, export the history regularly or have the Zap also write a log row to a table.