Added 429 advice for HTTP Request node (#2514)

Co-authored-by: Justin Ellingwood <justin@n8n.io>
This commit is contained in:
nik8n 2024-09-27 18:16:31 +02:00 committed by GitHub
parent c4265cf483
commit 01ef5cdfd1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -58,3 +58,26 @@ To resolve, review the selected credentials and make sure you can authenticate w
* Update permissions or scopes so that your API key or account can perform the operation you've selected.
* Format your generic credential in a different way.
* Generate a new API key or token with the appropriate permissions or scopes.
## 429 - The service is receiving too many requests from you
This error displays when the node receives a [429 error](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429){:target=_blank .external-link} from the service that you're calling. This often means that you have hit the rate limits of that service. You can find out more on the [Handling API rate limits](/integrations/builtin/rate-limits/) page.
To resolve the error, you can use one of the built-in options of the HTTP request node:
### Batching
Use this option to send requests in batches and introduce a delay between them.
1. In the HTTP Request node, select **Add Option > Batching**.
1. Set **Items per Batch** to the number of input items to include in each request.
1. Set **Batch Interval (ms)** to introduce a delay between requests in milliseconds. For example, to send one request to an API per second, set **Batch Interval (ms)** to `1000`.
### Retry on Fail
Use this option to retry the node after a failed attempt.
1. In the HTTP Request node, go to **Settings** and enable **Retry on Fail**.
1. Set **Max Tries** to the maximum number of times n8n should retry the node.
1. Set **Wait Between Tries (ms)** to the desired delay in milliseconds between retries. For example, to wait one second before retrying the request again, set **Wait Between Tries (ms)** to `1000`.