[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-run-history::en":3,"gloss-cluster-run-history::en":25,"gloss-next-run-history::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"run-history","no-code","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 \u002F 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\u002Foutput 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.","Run history is an automation platform's log of every execution — when it fired, what data passed each step, what failed, and the exact error message.",null,[11,14,17,19,22],{"slug":12,"name":13},"error-handler","Error Handler",{"slug":15,"name":16},"make","Make (Integromat)",{"slug":18,"name":18},"n8n",{"slug":20,"name":21},"scenario","Scenario",{"slug":23,"name":24},"workflow-automation","Workflow Automation",[26,30,34,37,40,43,46,49,52,55,58,61],{"slug":27,"category":5,"name":28,"updated_at":29},"action","Action","2026-08-24T02:46:36+00:00",{"slug":31,"category":5,"name":32,"updated_at":33},"aggregator","Aggregator","2026-08-24T02:46:37+00:00",{"slug":35,"category":5,"name":36,"updated_at":29},"airtable","Airtable",{"slug":38,"category":5,"name":39,"updated_at":29},"api","API",{"slug":41,"category":5,"name":42,"updated_at":29},"api-key","API Key",{"slug":44,"category":5,"name":45,"updated_at":33},"approval-workflow","Approval Workflow",{"slug":47,"category":5,"name":48,"updated_at":29},"automation-platform","Automation Platform",{"slug":50,"category":5,"name":51,"updated_at":29},"automation-recipe","Automation Recipe",{"slug":53,"category":5,"name":54,"updated_at":29},"backend-as-a-service","Backend-as-a-Service (BaaS)",{"slug":56,"category":5,"name":57,"updated_at":33},"backfill","Backfill",{"slug":59,"category":5,"name":60,"updated_at":29},"bubble","Bubble",{"slug":62,"category":5,"name":63,"updated_at":29},"business-logic","Business Logic"]