Lesson 32 · 4. Error Handling & Debugging · Last updated · By Dheeraj Sharma

Master AI Automation Workflows Debugging & Error Handling with Execution Logs

Learn Master AI Automation Workflows Debugging & Error Handling with Execution Logs in this comprehensive n8n tutorial. Step-by-step guide with video, code examples, and expert tips from the n8n Zero to Hero course.

Table of Contents

Overview

This lesson is part of the n8n AI Automation - Zero to Hero course, Section: 4. Error Handling & Debugging.

Watch the video above for the full tutorial, or read the written guide below.

What is the n8n Execution Log and how does it track workflow failures?

The n8n execution log records every workflow run in your project, both manual test executions and live production executions triggered automatically. Each entry captures the execution status (success, error, cancelled, running), the trigger type, start time, runtime duration, and execution ID. Clicking into any entry reveals the full input and output data at every node that ran, and double-clicking a failed node surfaces the exact error message and failure reason.

How to read n8n execution logs and fix failed workflow nodes

The execution log lives in the Executions tab of your n8n project. Two icons distinguish run types: a test icon marks manual executions where you clicked "Execute workflow" in the editor, and a live icon marks production executions fired automatically by an active trigger. You can filter by workflow name, status (error, success, cancelled, running, waiting), and date range. Searching by a specific data value inside execution records requires an n8n Pro plan and is not available on the Basic plan.

Each failed execution highlights the exact node where the error occurred. Clicking the errored node shows its input and output data; double-clicking opens the full error detail. Two concrete examples from the lesson: a Gmail node returned "sender invalid parameter value" because a webhook form submitted a malformed address (just @genaiunplugged with no domain), and a Notion node returned "bad request" because a PDF URL was passed to a field expecting an image URL. All upstream node outputs remain intact in the log, so you never need to re-run the workflow to reproduce the data context.

Per-workflow execution storage settings let you control what gets logged. Inside any workflow, open the three-dot menu and go to Settings to configure "Save failed production executions," "Save successful production executions," and "Save manual executions" individually, each switchable between Save and Do not save. On an errored node, two settings under Settings > On error change how failures propagate: "Continue past error on item in regular output" lets remaining items process but marks the overall execution as successful, silently hiding failures. "Continue using error output" routes failed items into a dedicated error branch with the error message appended, keeping failures visible for downstream handling such as triggering a separate error workflow.

Key Takeaways

  • The n8n execution log distinguishes manual runs (test icon) from production runs (live icon), so you always know whether a failure occurred during development or in live automation.
  • Each execution entry preserves the input and output data at every node that ran, letting you identify corrupt, missing, or misformatted data without recreating the execution from scratch.
  • The five most common n8n workflow failure causes are: misconfigured node settings, external service downtime (signaled by 4xx or 5xx HTTP errors), missing or incorrectly formatted data, expired credentials or API keys, and conditional logic that misses edge cases such as negative numbers or a boundary requiring "greater than or equal to" instead of "greater than."
  • The Retry on fail node setting retries a node up to three times with a configurable wait (default 1,000ms), which recovers from temporary service glitches but cannot fix permanent errors like an invalid email address.
  • The Continue using error output setting creates a success branch and an error branch on the node canvas, preventing silent suppression of failures and enabling handoff to a dedicated error workflow.

Next Steps

Continue your n8n journey with the full n8n AI Automation - Zero to Hero course.

Frequently Asked Questions

Manual executions in n8n run when you click the "Execute workflow" button in the editor and appear in the log with a test icon. Production executions fire automatically from an active trigger node, such as a schedule or webhook, and appear with a live icon. A workflow must contain an automatic trigger node before the active/inactive toggle is enabled and production executions can occur.

The 'Continue past error on item in regular output' setting passes failed items silently through the success path, so the execution log marks the entire run as successful even when individual records errored. 'Continue using error output' splits the node into two explicit branches on the canvas: a success branch for processed items and an error branch carrying the failed items with error messages appended, so failures remain visible and actionable.

The 'On error' option inside each node's Settings panel controls this behavior. By default it is set to 'Stop workflow,' which halts the entire execution on the first failure. Switching it to 'Continue using error output' lets the workflow process all remaining items, routes the failures, such as records with invalid or empty email addresses, into a dedicated error branch, and allows successful items to continue to the next node.

Workflow failures in n8n fall into five common categories: misconfigured node settings that do not handle unexpected inputs, external service downtime returning temporary or permanent HTTP 4xx or 5xx errors, missing or incorrectly formatted data such as empty or malformed email addresses, expired credentials or API keys causing authentication failures, and conditional logic that fails to account for edge cases like negative numbers or an off-by-one boundary condition.

Dheeraj Sharma

Dheeraj Sharma

AI Systems Builder
Creator of the n8n Zero to Hero course (42 lessons, 31+ hours). I help solopreneurs build AI systems that grow revenue without growing workload.

Get the n8n Mastery Bundle

All workflows, cheat sheets, and premium resources from the entire course in one package.

Get Premium Resources