Advanced Retry on Fail Except Known Errors Template

This workflow template provides advanced error handling for retry attempts in n8n, using a custom loop instead of built-in node retries. It allows granular control by distinguishing between expected (known) errors—triggering separate actions—and unexpected errors that warrant retries. The loop continues until the retry limit is reached, ensuring workflows don't fail prematurely on anticipated issues like non-existent resources.

Key components include a 'Set tries' node to track iterations, error filtering to check for known error patterns, and a stop node when limits are exceeded. Users replace a placeholder node with their target action, such as an API call lacking a dedicated existence check endpoint (e.g., Todoist completed tasks). Sticky notes guide optional configurations like max retries and error conditions.

Benefits include increased reliability for production automations, reduced unnecessary retries, and cost savings on API calls. It prevents infinite loops or abrupt failures, making workflows more resilient.

Ideal use cases: Real estate contract management for verifying document statuses via APIs without check endpoints; ERP integrations checking record existence; any scenario needing precise error differentiation. Copy into existing workflows for instant robustness.