Persisting Binary Data
There are fairly recent posts referencing N8N_BINARY_DATA_TTL and N8N_PERSISTED_BINARY_DATA_TTL however these variables are not listed.
These variables have since been deprecated. “Instead of relying on a TTL system for binary data, n8n currently cleans up binary data together with executions during pruning.”
I have not, however, found an explanation in the documentation of this approach to keeping the size of the binary data directory in check. The following pages/sections could benefit from an explanation:
- Binary data filesystem mode
- Execution data - Enable data pruning
- Environment variables reference - Binary Data
- Environment variables reference - Executions
The following limitation should also be more clearly communicated:
External storage for binary data | n8n Docs: “Binary data pruning operates on the active binary data mode. For example, if your instance stored data in S3, and you later switched to filesystem mode, n8n only prunes binary data in the filesystem. This may change in future.”