n8n Foutafhandeling

# n8n Error Handling: Loud, Structured, and Recoverable ## Core Principles **Failures should be:** - **Loud** — immediately visible, never silent - **Structured** — consistent format with context - **Recoverable** — actionable next steps, retry logic, fallbacks --- ## Essential Error Handling Patterns ### 1. **Wrap Critical Nodes with Try-Catch Logic** Use a pattern for any node that could fail: ``` [Node A] → [If/Switch: Check for error] → [Log Error] → [Retry or Fallback] ``` **Implementation:** - Set node's "Continue on Fail" = `ON` (not automatic, explicit) - Immediately follow with an **IF node** checking `node.executionStatus === 'error'` - Route errors to dedicated error handler

Bron: github.com/czlonkowski/n8n-skills/tree/HEAD/skills/n8n-error-handling · Licentie: MIT