Timeout in node HTTP after 2:01 minutes

Questions
1

Describe the problem/error/question

Hi,
In a workflow I have an HTTP node that makes a call to a third part software’s API.
In the UI of that third part software I can see that the action has been executed and the output has been throwed, but in N(N I’m geting always the same error (see section below).
The same node, if the execution lasts less than 2 minutes, does not throw the “time out” error and the flow continues without problems.
I’ve checked the timeouts of the nginx proxy, I’ve configured the workflow timeout (now it’s an hour), and the API’s timeout in the third part software.

What is the error message (if any)?

[
{
“Message”: “Timed out.”
}
]

Please share your workflow

Share the output returned by the last node

[
{
“Message”: “Timed out.”
}
]

Information on your n8n setup

  • n8n version: 1.25.1
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: Ubuntu 22.04
2

Hi, I activated the debug and this is the error I’m getting:

{“level”:“debug”,“message”:“Running node "Snapshot Process Result" finished successfully”,“metadata”:{“file”:“LoggerProxy.js”,“function”:“exports.debug”,“node”:“Snapshot Process Result”,“timestamp”:“2024-03-05T14:48:27.128Z”,“workflowId”:“0at8AQzdztruoMbl”}}

{“level”:“debug”,“message”:“Start processing node "Snapshot error"”,“metadata”:{“file”:“LoggerProxy.js”,“function”:“exports.debug”,“node”:“Snapshot error”,“timestamp”:“2024-03-05T14:48:27.129Z”,“workflowId”:“0at8AQzdztruoMbl”}}

{“level”:“debug”,“message”:“Running node "Snapshot error" started”,“metadata”:{“file”:“LoggerProxy.js”,“function”:“exports.debug”,“node”:“Snapshot error”,“timestamp”:“2024-03-05T14:48:27.129Z”,“workflowId”:“0at8AQzdztruoMbl”}}

{“level”:“debug”,“message”:“Running node "Snapshot error" finished with error”,“metadata”:{“file”:“LoggerProxy.js”,“function”:“exports.debug”,“node”:“Snapshot error”,“timestamp”:“2024-03-05T14:48:27.173Z”,“workflowId”:“0at8AQzdztruoMbl”}}

{“level”:“verbose”,“message”:“Workflow execution finished with error”,“metadata”:{“error”:{“description”:“TypeError”,“lineNumber”:2,“message”:“Cannot read properties of undefined (reading ‘1’) [line 2]”,“stack”:“TypeError: Cannot read properties of undefined (reading ‘1’)\n at /usr/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Code:2:89\n at /usr/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Code:7:2\n at VM2 Wrapper.apply (/usr/lib/node_modules/n8n/node_modules/@n8n/vm2/lib/bridge.js:485:11)\n at NodeVM.run (/usr/lib/node_modules/n8n/node_modules/@n8n/vm2/lib/nodevm.js:497:23)\n at JavaScriptSandbox.runCodeAllItems (/usr/lib/node_modules/n8n/node_modules/n8n-nodes-base/nodes/Code/JavaScriptSandbox.ts:70:36)\n at Object.execute (/usr/lib/node_modules/n8n/node_modules/n8n-nodes-base/nodes/Code/Code.node.ts:135:28)\n at Workflow.runNode (/usr/lib/node_modules/n8n/node_modules/n8n-workflow/src/Workflow.ts:1322:31)\n at /usr/lib/node_modules/n8n/node_modules/n8n-core/src/WorkflowExecute.ts:1046:44\n at processTicksAndRejections (node:internal/process/task_queues:95:5)”},“file”:“LoggerProxy.js”,“function”:“exports.verbose”,“timestamp”:“2024-03-05T14:48:27.174Z”,“workflowId”:“0at8AQzdztruoMbl”}}

thanks in advance
Antonio

3

Hey @Zambot1971,

Just to check… In the output of the http request node are you seeing json that says “Timed Out”? Is there anything else in there?

4

Hi,
thanks for your response.
Yes, the only message that I can see is the one that says:
[
{
“Message”: “Timed out.”
}
]

I’ve checked all the deamons (nginx, tomcat to the other side) but I cant see figure out where this timeout is.
I’ve also configured the workflow timeout to 1 hour, but still I got the error.
The same execution with less endpoints, that lasts less than 2 minutes, does not throw the error message.
kind regards

5

Hey @Zambot1971,

As far as I know if there is an timeout we wouldn’t show what you are seeing and it would be a large red message showing a timeout unless you are always outputting data.

Can you share the workflow?

6

Thank Jou Jon, never mind, I’m going to manage the task in a different way on the endpoint.
Best regards

1 Like
7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.