Data pruning needed in n8n
- Feb 13
- 1 min read
What this means (non-technical)
Data pruning is the automatic deletion of old execution records. If pruning is not configured, n8n keeps all execution data forever.
Over time, this creates unnecessary database growth.
What usually goes wrong
Without pruning:
Execution history grows endlessly.
The UI becomes slower to load.
Backup sizes increase.
Storage costs rise.
Eventually, disk space can run out.
This usually builds slowly, so it’s easy to ignore until performance drops noticeably.
When this becomes urgent
This becomes urgent when:
Disk space usage steadily increases.
Backups take longer than expected.
Execution history is rarely needed beyond a certain time.
You run high-frequency workflows.
The longer pruning is delayed, the larger the cleanup task becomes.
Detect issues in your n8n workflows
|
Definitions
Data pruning: The automatic removal of old execution records.
Retention period: The amount of time execution data is kept before being deleted.
Disclaimer
This article highlights common patterns and risks seen in real-world n8n workflows. It’s meant to help you build more confidently and avoid surprises as your automation grows. Behavior can vary depending on your setup, version, and configuration.