ETIMEDOUT error when even the workflow is activated

Questions
1

Hi I just notice that when the workflow is not processing any data the application is automatically stopped or timed out even the workflow is on active status, is there any changes I need to change on my installation or add something on my workflow to prevent this issue?

image

2

Hey @rodskie123,

Any more details? What is stopping, what is the workflow doing, how is it running?

That error just looks like a standard network timeout so it could be anything.

3

Hi Jon,

the workflow works only when the gmail receive an email attachment, the IMAP node will automatically process it to send the attachment to FTP server which is on my local server, I notice if the workflow not receiving any email the my n8n application will automatically time out even n8n application is still open on my web browser but the status is “connection lost”

error code


Error: read ETIMEDOUT
    at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
  errno: -110,
  code: 'ETIMEDOUT',
  syscall: 'read',
  source: 'socket'
4

Hey @rodskie123,

The application shouldn’t time out, how is n8n running and is the workflow running in the background or are you pressing execute workflow? Does the n8n execution log show anything and where are you seeing that error message is it in the n8n console log or in the interface?