Hi @marexxxxxxx, welcome to the community!
Since you’re on version 2.1.5 and using Task Runners, a common “gotcha” is the shared filesystem . Even if you’ve set the N8N_RESTRICT_FILE_ACCESS_TO variable correctly, both the main n8n container and the task-runner container need to have the exact same volume mounted at the exact same path. If they aren’t perfectly synced, the task-runner might be trying to write to a directory that only exists in its own isolated ephemeral storage.
In Coolify, double-check that your files volume is actually attached to bothservices in your compose file.Just as a test, have you tried writing to a subdirectory within the default /home/node/.n8n/ folder? Sometimes that bypasses external mount headaches.
merging files inside a loop using binary nodes can be really tough on memory. Most people in the community find it much smoother to use ffmpeg via the Execute Command node if your Docker image supports it. It’s usually faster and less prone to crashing the workflow.
By the way, could you share how you defined the volumes for the task-runner in your compose file?