Run History

Run history (also called execution history or the execution log) is the record every automation platform keeps of each time a workflow ran — when it fired, what data flowed through each step, which steps succeeded or failed, and the exact error message when something broke. In Make it's the scenario "History" tab with a bubble map of each run; in Zapier it's "Zap history / Task history"; in n8n it's the "Executions" list. Why it matters: run history is your primary debugging tool in no-code automation. When a customer says "my Slack alert didn't fire," you open run history, find that execution, and inspect the actual payload each module received. Practical note: check whether the platform stores full input/output data or only metadata, and for how long — retention is often shorter on cheaper plans, and some platforms disable data logging by default to save storage. Enable it while building, and turn on failure notifications so a broken run emails you instead of silently disappearing.