My HTTP Request component is generating a “too many requests” error despite the fact that I am deliberately only sending one request! I have set the batch size to be 1 and the batch interval to be zero. The idea was to avoid this error.
What is the error message (if any)?
Too many requests
Please share your workflow
NOTE 1: The HTTP Request component has a batchSize of 1 and a batchInterval of 0.
Note 2: I am using a manual trigger in my workflow, but I cannot seem to make it appear in my workflow diagram below. Could someone tell me how to
make everything appear in a workflow diagram?
Share the output returned by the last node
Issues:
The service is receiving too many requests from you
Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.
```
<your workflow>
```
That implies to any JSON output you would like to share with us.
Make sure that you have removed any sensitive information from your workflow and include dummy or pinned data with it!
How many input items to the HTTP Request node do you have?
Setting batching interval to 0 implies you are disabling batching. This definitely not going to help you.
If the set of items in the node immediate preceding HTTP Request node is large but you need to run HTTP Request node only once, you can set “Execute Once” to true in the Settings of the node.
However, if you do need to make as many GET requests as there are incoming items, increase the Batch Interval value to make sure you do no violate the limits imposed on the API.
Please be advised that your “Tip for sharing information” did not help. I already knew to put the JSON in the code block (as I was able to put the HTTP node in). What I did not know was how to put in the entire workflow. Previously, I was attempting to copy the nodes to my clipboard and pasting them between the code blocks – only to discover that apparently the n8n user interface only copies a single node at a time and attempting to copy one node after another and pasting them causes JSON errors. That is why I was asking how to put in the workflows. I have since learned that I can download a complete workflow, then copy its contents to the code block, like so:
Please note that I did change the HTTP request so that it does make the request once, as you suggested. There are really no input items processed by the request node, because I am using a manual trigger, which apparently puts in an empty item to the Request node. In any event, I am still getting “too many requests” errors when I run the workflow. I am suspecting that there may be a bug in the request node. Maybe in its error handling? I have seen this “too many requests” error occur when I got an unauthorized error due to forgetting to put in the authentication for a website.
Sorry if that did not make it clear to you. However, you are still not doing it right. Just copy the whole workflow and paste it into Community post in between the pair of triple ticks (as what advised initially). There is no need in downloading workflows. It is an unnecesary step, just copy and paste!
Sometimes copying might fail, just repeat it again until you see a confirmation the workflow was copied (unless your browser have some plugins or else that prevent copying).
I have seen this “too many requests” error occur when I got an unauthorized error due to forgetting to put in the authentication for a website.
The error comes from the API, it is not a self-made message by the node. Please refer to your API documentation to figure out what you are doing wrong.
In your workflow you are using a LinkedIn web page which requires an authenticated access. I do not believe this is a right aproach. You probably want a proper API endpoint, not the web page as such that is not publicly available (available without a login).
Sorry if that did not make it clear to you. However, you are still not doing it right. Just copy the whole workflow and paste it into the Community post in between the pair of triple ticks (as what advised initially). There is no need in downloading workflows. It is an unnecesary step, just copy and paste!
Ummm… did you see the new workflow that I put up in my previous reply??? As I said in my last reply, I figured out how to copy the workflow, which involved downloading them. This was necessary because “copying” and “pasting” nodes does not create good JSON, and the n8n system does not allow the actual copying of full workflows. Besides: downloading workflows is a good idea anyway because there seems to be a bug in the filter node that requires me to restart n8n periodically, which curiously enough resets the entire system. So downloading the workflows is a necessesity anyway.
Nevertheless, this entire subject is moot. I have the workflow copied and displayed. Let’s move on.
The error comes from the API, it is not a self-made message by the node. Please refer to your API documentation to figure out what you are doing wrong.
In your workflow you are using a LinkedIn web page which requires an authenticated access. I do not believe this is a right aproach. You probably want a proper API endpoint, not the web page as such that is not publicly available (available without a login).
There is no “API” on linkedIn that gives the information that I am seeking. And if there was, I would still need to authenticate it in order to access it. Are you saying that the HTTP node cannot access pages using HTTP that are not APIs or that require authentication? If that is so, then that is a serious inadequacy in the node, not my use of it.
If the error is coming from the API, why am I not seeing it on the network monitoring that I am doing? When monitoring the attempt by the HTTP node to access the page, I am seeing wss errors, not 423 errors. I am also seeing “failure to connect” errors.
Furthermore, if I change the URL from https://www.linkedin.com/jobs/collections/recommended
to https://www.linkedin.com/jobs
I am seeing the page is being returned without problems (a 200 reply) and I am getting the contents of the page. This tells me that the problem has something to do with the way the HTTP node is handling the first page, not what the page is returning.