Automation glossary

Run History

Run history is the log of an automation’s past executions, showing when each ran, the data each step received and returned, and whether it succeeded.

In plain language

It is the first place to look when someone asks “did the automation run, and what did it do?”

Example

Zapier’s Zap history shows a failed step with the exact error message and the input data.

Monitoring · Audit Trail · Error Handling · Trigger

Common misconception

Run history is not kept forever; platforms keep it for a limited time, so long-term records need separate logging.

Implementation guidance

Check run history when debugging, know your platform’s retention period, avoid logging secrets, and export key events if you need a lasting record.

Primary references

← Browse every glossary term