Large Payload causing silent failures

Questions
1

when processing large binary data through multiple nodes, executions fail without a clear stack trace. Could this be related to the binary data mode and database storage strategy?

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the 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:
2

Hey @Ayomide_Breakthroug1

That’s very likely.

By default, binary data may be stored in the database, which is not optimal for large payloads.

Switch to:

N8N_DEFAULT_BINARY_DATA_MODE=filesystem

This moves binary storage to disk and prevents database bloat, serialization overhead, and memory spikes during execution.

3

Hi @Ayomide_Breakthroug1 Welcome to the community!
As n8n stores binary data in ram this is certain to be happened, if you are self hosting first increase the ram capacity.

1 Like
4

you are so knowledgeable, will like to connect with you

1 Like
5

Hey, hard to say much without more context — can you share your workflow JSON, the n8n version you’re on, whether you’re using filesystem or default binary data mode, and any error messages from the execution logs or browser console? Even a screenshot of where it fails would help narrow this down.

6

Hey, hard to say much without more detail here — can you share your actual workflow JSON, what n8n version you’re on, how you’re running it (Docker/npm/cloud), and whether you see anything in the server logs when it fails? Also knowing your binary data mode setting (default vs filesystem) and roughly how large the payloads are would help narrow this down.