Sub-Workflow Executions with "Save successfull production executions" to "Do not save"

[Andreas_Pointner]

Describe the problem/error/question

I’m having a workflow that is set to “Save successfull production executions” to “Do not save”.
In that workflow I’m executing another workflow that only works if the SUB-Workflows setting for “Save successfull production executions” is set to “Save”. If the mode (Run Subtask - Create Docx) is switched to “Do not save” I get the error:

ENOENT: no such file or directory …

What is the error message (if any)?

Please share your workflow

Information on your n8n setup

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

Debug info

core

• n8nVersion: 1.67.1
• platform: docker (self-hosted)
• nodeJsVersion: 20.18.0
• database: postgres
• executionMode: scaling
• concurrency: -1

storage

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

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

[ria]

Hi @Andreas_Pointner

I didn’t see any issues with switching from Save to Do Not Save.
The error you’re getting is indicating a problem with some binary data processing in your subworkflow.

Can you share that workflow here so we can see what could be the cause of that error?

Tip for sharing your workflow in the forum

Pasting your n8n workflow

---

Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.

```
<your workflow>
```

Make sure that you’ve removed any sensitive information from your workflow and include dummy data or pinned data as much as you can!

---

[Andreas_Pointner]

Sure but there is no binary data involved, this is why i’m confused.

This is the workflow

[ria]

Hi @Andreas_Pointner

I meant the workflow with id XMIJ3PuHcJlLZC7z named Run Subtask - Create Docx
As it seems that the error is coming from that workflow.

[Andreas_Pointner]

Hi Ria,

the workflow is not triggered at all. The sub-workflow has no executions (no successfull nor failed ones). The error is only in the main workflow.

I’ll gonna send you the other workflow next week. Thanks for checking.

[Andreas_Pointner]

[ria]

Hi @Andreas_Pointner

Can you try to set the N8N_DEFAULT_BINARY_DATA_MODE variable to default and see if that helps?

Scaling binary data in n8n | n8n Docs

[Andreas_Pointner]

Hi ria,

looks like i configured my instance with an outdated verision of the documenation. Somehow I did not see that queue mode is not working with binary mode set to filesystem.

I think the problem is that if the worker is running on another host then filesystem won’t work that easy.

Thanks for your help.