When working with n8n, it’s easy to overlook retry and backoff settings—especially in HTTP Request nodes that interact with external APIs. But a missing retry configuration can make your workflow fragile, causing it to fail whenever an API responds with a transient error or rate limit.
In this example, Flowlint flags an R1: Node is missing retry/backoff configuration issue, highlighting the importance of enabling "Retry on Fail" to build more resilient automations. Below is a quick look at the configuration before and after applying the recommended fix, along with why this small adjustment makes a big difference in workflow reliability.
In the node properties, enable "Retry on Fail" under Options.
Before applying the fix, the n8n HTTP Request node contains only the default settings—meaning no retry or backoff behavior is defined. In this state, any API timeout, rate limit, or momentary outage will immediately propagate a error (if n8n HTTP Request node has "On error" set to "Continue using error") or will stop the workflow (if n8n HTTP Request node has "On error" set to "Stop Workflow"). This is especially problematic for scheduled or multi-step automations that depend on consistent API availability.`
In the screenshot, you can see:
- Retry on Fail is disabled
- No additional retry configuration appears under Options
Configuration of n8n HTTP Request node before fix
Configuration of n8n HTTP Request node before fix:
Configuration of n8n HTTP Request node after fix
After enabling Retry on Fail in n8n HTTP Request node, the Options panel exposes settings such as retry attempts, retry delay, and backoff mode. These parameters allow you to fine-tune how the node reacts to failures—attempting the request again with incremental delays instead of failing outright.
Configuration of n8n HTTP Request node after fix:
This improved configuration ensures:
- The workflow continues even when APIs momentarily respond with errors
- Backoff behavior prevents hammering APIs and respects rate limits
- Overall workflow stability increases, especially for long-running or unattended executions
It is important to set retry and backoff configuration for n8n HTTP Request node to avoid cases when API returns error and workflow fails.
