The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →To retry a failed n8n HTTP request, open the HTTP Request node’s Settings, turn on Retry on Fail, and set Max Tries and Wait Between Tries (ms). This gives you a configurable wait between attempts; the official n8n documentation reviewed does not describe this built-in setting as exponential backoff. For rate limits, pace requests with HTTP Request batching or a Loop Over Items and Wait pattern, using the API provider’s documented limits to choose the delay.
Choose the right retry approach
Retries and rate-limit pacing solve related but different problems. Retry on Fail repeats a failed node request. Batching and loop-and-wait patterns control the rate at which successive items generate requests. Use a custom retry loop when the delay needs to grow or follow other workflow logic.
| Approach | Best fit | Main configuration |
|---|---|---|
| Retry on Fail | Repeat a failed HTTP Request after a fixed wait | Max Tries and Wait Between Tries (ms); see the HTTP Request documentation. |
| HTTP Request batching | Control groups of requests made for many input items | Items per Batch and Batch Interval (ms); see the HTTP Request documentation and n8n rate-limit guide. |
| Loop Over Items plus Wait | Explicitly pace item-by-item or chunked requests | Batch size and pause between iterations; see the n8n rate-limit guide. |
| Custom retry loop | Apply a custom schedule, such as increasing delays | Retry count, initial delay, and delay-update expression; see the n8n community workflow templates. |
Set a fixed retry wait on an HTTP Request node
-
Open the workflow and select the HTTP Request node that calls the API.
-
Open the node’s Settings tab and enable Retry on Fail.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.#1 Best Overall
-
Set Max Tries to the number of attempts you want the node to make, and set Wait Between Tries (ms) to the delay between them.
-
Save the node and run a test execution. Check the execution details to confirm whether a failed request is retried and whether the final result is what the workflow should handle.
Rank #2
APIs: A Strategy Guide: Creating Channels with Application Programming Interfaces- Used Book in Good Condition
The HTTP Request documentation uses 1000 ms as an example of a one-second wait. That is an example value, not a universal recommendation: select a delay that fits the API’s limits and behavior. The documented setting is a configurable wait, not a documented automatic exponential schedule.
Handle rate limits by pacing requests
If a workflow processes many input items, each item may lead to another API request. A retry setting alone does not necessarily pace all successful requests. To control request flow, choose one of these patterns:
Use HTTP Request batching
Configure the HTTP Request node’s Items per Batch and Batch Interval (ms) so items are sent in groups with a pause between batches. This suits workflows where requests can be grouped and the API’s limit can be met through a known batch size and interval.
Use Loop Over Items with Wait
For more explicit control, process items through Loop Over Items and place a Wait node between iterations or chunks. Set the batch size and pause to match the target API’s documented rate limit.
n8n’s rate-limit guide advises setting the retry wait longer than the rate limit; its example for an API allowing one request per second uses a one-second wait. Treat this as an illustrative case, not a setting that applies to every service. Check the provider’s current API documentation for its limits and how it signals throttling.
Build exponential backoff with custom workflow logic
If each retry should wait longer than the previous one, use a custom workflow loop rather than assuming the built-in Retry on Fail setting will increase its delay. The n8n community template Advanced retry and delay logic demonstrates a loop built with Set, If, and Wait nodes. One optional delay update shown in that example is {{$json.delay_seconds * 2}}, which doubles the stored delay after an attempt.
Best Value
In a custom loop, define the retry count and initial delay, evaluate whether another attempt is allowed, wait for the current delay, and update the delay before looping back to the request. The expression is an example from a community template, not a guarantee of native node behavior; adapt and test the workflow for your own request and failure conditions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check whether retrying is safe for the operation
Whether a request can safely be repeated depends on the API and the operation. Repeating a read request may have different consequences from repeating a write that creates or changes a record. Before enabling retries for an operation that can have side effects, consult the provider’s documentation for its retry guidance and protections against duplicate effects. The n8n rate-limit guidance points users to the target API’s own documentation; it does not define those API-specific policies.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
