To retry a failed n8n HTTP Request, open the node’s Settings, enable Retry on Fail, and set Max Tries and Wait Between Tries (ms). That setting provides a configured wait between attempts; the n8n documentation reviewed does not describe it as automatic exponential backoff. To pace a stream of requests, configure HTTP Request batching or use a Loop Over Items node with a Wait node. For a growing delay, build custom retry logic.
Choose the right kind of retry
Retrying a request that failed and pacing a sequence of requests solve different problems. A retry gives one failed operation another attempt; batching or a loop with a wait controls how quickly successive items are sent. Pick the approach that matches the failure pattern and the target API’s documented limits.
As an Amazon Associate I earn from qualifying purchases.
| Approach | Best fit | Main settings |
|---|---|---|
| Retry on Fail | Retrying a failed node request after a fixed wait | Max Tries; Wait Between Tries (ms) |
| HTTP Request batching | Sending many input items in controlled groups | Items per Batch; Batch Interval (ms) |
| Loop Over Items plus Wait | Explicit item-by-item or chunked pacing | Batch size; pause between iterations |
| Custom retry loop | A retry schedule with custom behavior, such as an increasing delay | Retry count; initial delay; delay-update expression |
Configure Retry on Fail for a fixed wait
- Open the HTTP Request node and select Settings.
- Enable Retry on Fail.
- Set Max Tries to the number of attempts you want the node to make.
- Set Wait Between Tries (ms) to the pause between attempts. The n8n HTTP Request documentation gives
1000ms as an example of a one-second wait.
See the n8n HTTP Request documentation for the node’s retry settings. The documented wait is configurable; do not assume the native setting increases the delay exponentially.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesHandle rate limits by pacing requests
If several input items are triggering rate-limit errors, add spacing between requests rather than relying only on retrying failures. The appropriate interval depends on the particular API and operation. Check the provider’s current documentation for its limits and error behavior before choosing a delay.
#1 Best Overall
Use HTTP Request batching
Configure the HTTP Request node’s batching options: set how many items to send per batch and the Batch Interval (ms) between batches. The n8n rate-limit guide recommends setting the retry wait longer than the API’s rate limit; its example for a service allowing one request per second uses a one-second wait. Treat that as an example, not a universal setting.
Use Loop Over Items with Wait
For explicit item-by-item or chunked pacing, route items through Loop Over Items and place a Wait node between calls or iterations. Set the batch size and pause to suit the API’s published limits. See n8n’s rate-limit guidance and HTTP Request documentation.
Rank #2
- Used Book in Good Condition
Build exponential backoff with custom workflow logic
If each retry should wait longer than the last, use a custom loop that tracks the retry count and current delay, checks whether another attempt is allowed, waits, and updates the delay before looping. The n8n community template Advanced retry and delay logic demonstrates a pattern using Set, If, and Wait nodes. Its optional expression {{$json.delay_seconds * 2}} doubles the stored delay; this is an example of custom workflow logic, not a native Retry on Fail schedule.
Recommended Free Tools
Check retry safety before repeating a request
Whether a retry is safe depends on the target API and operation. Repeating a write could create duplicate effects, and the n8n guidance reviewed does not establish how every service handles response headers or repeated requests. Consult the provider’s current API documentation before retrying operations that create or change data.
Quick Recap
Best Value
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.
