HTTP request / 3 min timeout

[Amine_Ben]

Describe the problem/error/question

What is the error message (if any)?

Hello,

Http request node stops the request at 3 min. I have even added a timeout at around 8 min but still, the request dropped at 3 min limit

{
“meta”: {
“instanceId”: “865a0dee3c19231471d216f0ba2691fcd395f39f4385e7cbb38a4acb62dd7ba2”
},
“nodes”: [
{
“parameters”: {
“method”: “POST”,
“url”: “https://hook.us1.make.com/xxxxxxxxxxx”,
“options”: {
“timeout”: 500000
}
},
“id”: “69980473-618b-4c20-adbc-cf90037e4dcc”,
“name”: “HTTP Request”,
“type”: “n8n-nodes-base.httpRequest”,
“typeVersion”: 4.1,
“position”: [
340,
400
],
“retryOnFail”: false,
“alwaysOutputData”: false,
“executeOnce”: false
}
],
“connections”: {}
}

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

• n8n version: Self Hosted
• Database (default: SQLite): pg
• n8n EXECUTIONS_PROCESS setting (default: own, main): default
• Running n8n via (Docker, npm, n8n cloud, desktop app): GCP
• Operating system:

[Amine_Ben]

[Amine_Ben]

so for more details:

the url than I requesting could take 5 min to process the request and send back the response

But the HTTP post request, stop at 3 min, it seems there a limitation around this Node??

I have been testing a LOT without success

[prononext]

Depending on how you setup your n8n, it could be in your workflow settings, or have something to do with your proxy connection keepalive. It is just strange that the execution is a success and not a failure.

I am just interested what make.com can do that n8n cannot

[Amine_Ben]

Thanks for your answer

You can achieve the same results in both platforms, maybe MAKE is more effective.

Where I can find the option keep alive?

[Amine_Ben]

The problem is that the http request node don’t wait until a certain time to get back results, instead it just outputs status 200 “Accepted” after 3 min automatically

[Amine_Ben]

I discovered that this limitation is from the requested server