Unstable API request to Baserow.io

Technical Help
, ,
1

Please fill in the questionnaire below.

I using Baserow.io.

Describe the problem

My API requests to Baserow.io have been frequently returning errors, so I need to keep retrying the requests until they succeed. This has been happening since yesterday.

{
“errorMessage”: “The connection to the server was closed unexpectedly, perhaps it is offline. You can retry the request immediately or wait and retry later.”,
“errorDetails”: {
“rawErrorMessage”: [
“read ECONNRESET”,
“read ECONNRESET”
],
“httpCode”: “ECONNRESET”
},
“n8nDetails”: {
“nodeName”: “Pega Links”,
“nodeType”: “n8n-nodes-base.baserow”,
“nodeVersion”: 1,
“resource”: “row”,
“operation”: “getAll”,
“time”: “16/12/2024, 12:08:10”,
“n8nVersion”: “1.71.3 (Self Hosted)”,
“binaryDataMode”: “default”,
“stackTrace”: [
“NodeApiError: The connection to the server was closed unexpectedly, perhaps it is offline. You can retry the request immediately or wait and retry later.”,
" at ExecuteContext.getJwtToken (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Baserow/GenericFunctions.js:66:15)“,
" at processTicksAndRejections (node:internal/process/task_queues:95:5)”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Baserow/Baserow.node.js:124:26)“,
" at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:741:19)”,
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:724:51",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1155:20"
]
}
}

2

Hi @Ivan I am not aware of any service disruption on our side. How many requests you are making?

3

Hi @petrs !
Not many. I’ve been using it for months and nothing has changed, but this issue started from yesterday to today. Today I counted approximately 60 requests, with more than 10 returning errors. As you can see in the image, there aren’t many requests, and they have a good interval between them.

baserow
baserow1536×934 122 KB

4

Olá estou com o mesmo problema. Alguém pode ajudar?

[Translated] Hello, I have the same problem. Can anyone help?

5

Honestly it looks like a network problem to me rather than a problem with baserow.io as a service.

6

It can’t be a network issue, as I have several workflows making requests to different APIs on the same server, within the same N8N instance, and the error only occurs with requests made to Baserow.io. Furthermore, it was working stably until 12/14, and I haven’t made any changes in the past few months while it has been running stably.

1 Like
7

Exatamente o meu mesmo problema. Agora está retornando o erro 502:

{
  "errorMessage": "Bad gateway - the service failed to handle your request",
  "errorDescription": "502 - \"\"",
  "errorDetails": {
    "rawErrorMessage": [
      "502 - \"\""
    ],
    "httpCode": "502"
  },
  "n8nDetails": {
    "nodeName": "PREENCHE BANCO",
    "nodeType": "n8n-nodes-base.baserow",
    "nodeVersion": 1,
    "resource": "row",
    "operation": "update",
    "time": "17/12/2024, 10:43:29",
    "n8nVersion": "1.71.3 (Self Hosted)",
    "binaryDataMode": "default",
    "stackTrace": [
      "NodeApiError: Bad gateway - the service failed to handle your request",
      "    at ExecuteContext.baserowApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Baserow/GenericFunctions.js:31:15)",
      "    at processTicksAndRejections (node:internal/process/task_queues:95:5)",
      "    at ExecuteContext.getTableFields (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Baserow/GenericFunctions.js:87:16)",
      "    at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Baserow/Baserow.node.js:125:24)",
      "    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:741:19)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:724:51",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1155:20"
    ]
  }
}
8

Please use English on this forum :slight_smile:

Maybe @bram will know what the problem could be.

9

Hey @Ivan, @TaislanSantos, it’s a bit difficult to say for both errors based on the out here, to be honest. Would you both be able to share more information, like which table the request was related to, what the payload and what the payload of the API request looked like?

10

Hi @petrs , @bram ! Thank you for trying to help me. It has become stable again. I’m not sure what happened, but I’ve been using Baserow for some time, and it has served me very well until now. Recently, I started experiencing some issues. First, it was the webhooks that started taking too long to trigger and eventually stopped working. Now, there was this situation of rejecting requests. I hope it goes back to working as it did before.

1 Like
11

Hey @Ivan, you’re welcome. I’m sorry to hear that you’re experiencing multiple problems recently with Baserow. We’re doing our absolute best to make sure that you have the best experience using the platform.

We’ve taken several steps to prevent the webhooks problem from happening in the future. One of them is monitoring the backend worker queue length. If it exceeds more than 10 tasks, which could be more than 10 webhook calls, then we’ll immediately be notified about it. You also see the health of this on our status page https://status.baserow.org/ in the task “Task queue size” item. This allows us to immediately take action, if it happens again.

To figure out what exactly went wrong with your n8n calls, and to prevent it in the future, we do need more information on the request that n8n made to Baserow, like I described in my previous message. :slight_smile: