ERROR on Coda node. connect ETIMEDOUT


Describe the issue/error/question

Workflow stops on the error:

What is the error message (if any)?

{"context":{},"name":"NodeApiError","cause":{"message":"connect ETIMEDOUT","name":"Error","stack":"Error: connect ETIMEDOUT\n    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1247:16)","code":"ETIMEDOUT"},"timestamp":1661419334081,"message":"UNKNOWN ERROR - check the detailed error for more information","node":{"parameters":{"resource":"table","operation":"getAllRows","docId":"MSpwMW8WvC","tableId":"grid-KZeKzaB4yP","returnAll":true,"options":{}},"name":"Coda","type":"n8n-nodes-base.coda","typeVersion":1,"position":[400,-120],"id":"1dd91a16-da7f-46a7-a980-bd639a122d16","credentials":{"codaApi":{"id":"12","name":"Coda account"}}},"httpCode":"ETIMEDOUT","description":"connect ETIMEDOUT"}

It seemed to work. Such errors pop up from time to time.
How to correct the error?
Thank you very much!

Information on your n8n setup

  • n8n version: 0.188.0
  • Database you’re using (default: SQLite): SQLite
  • Running n8n with the execution process [own(default), main]:
  • Running n8n via [Docker, npm,, desktop app]: Docker

Hi @Mikhail, seeing this only happens from time to time my best guess is that you’re affected by temporary network connectivity issues. The ETIMEDOUT error indicates that a “(…) send request failed because the connected party did not properly respond after a period of time (…)”.

As a first step you might want to enable the retry options on your Coda node like so:


This way, n8n would re-try the failed request automatically.

1 Like

Hi @MutedJam !
Thank you so much for the quick response!
I made the necessary additions and will keep track for a few days and then report back here with the results

1 Like

Hi @MutedJam !

A few days of testing showed no errors in work.
Most likely, the problem is solved!

1 Like

Glad to hear, thx so much for confirming!