Workflow failing without any visible error

Describe the problem/error/question

Q: Why I don’t have any error information in n8n but only by searching in the logs?

The following workflow read 5 json files from dropbox. They are backup data from a sqlite table:


As you can see that table is 320K raws.

I’ve splited data into four 13KB json files and they are loaded by the workflow using a Dropbox download node.

The workflow is designed to load all that data into a NocoDB database. But, in NocoDB, I only got 24K rows:

What is the error message (if any)?

In the workflow itself, there is no error (unless its status):

But, in n8n log I’ve found this:

502 - {"status":"error","code":502,"message":"Application failed to respond","request_id":"S2ovPexXSmmW5ZiJHewIiw_2654280189"}

AxiosError: Request failed with status code 502

    at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:19:12)

    at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:599:11)

    at IncomingMessage.emit (node:events:531:35)

    at IncomingMessage.emit (node:domain:488:12)

    at endReadableNT (node:internal/streams/readable:1696:12)

    at processTicksAndRejections (node:internal/process/task_queues:82:21)

    at Axios.request (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/Axios.js:45:41)

    at processTicksAndRejections (node:internal/process/task_queues:95:5)

    at requestFn (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:615:33)

    at proxyRequestToAxios (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:618:26)

    at ExecuteContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1299:16)

    at ExecuteContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1666:20)

    at ExecuteContext.apiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/NocoDB/GenericFunctions.js:31:12)

    at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/NocoDB/NocoDB.node.js:347:36)

    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:732:19)

    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:716:51

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
instance information

Debug info

core

  • n8nVersion: 1.70.3
  • platform: npm
  • nodeJsVersion: 20.18.0
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: de9eaa3a-de5a-4b44-983a-486ec843a673

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 168 hours
  • maxCount: 50000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/131.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2024-12-06T22:27:22.067Z

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

Hey @PLegoux

I suspect the instance ran out of memory, I would do the nocodb create in a sub workflow so that the memory is cleared on each loop so that you at not keeping all that data in memory.

1 Like

Thank you @Jon

I will try that, I will come back here to say if this is the solution

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