Execution progress saving enabled in n8n
- Feb 13
- 1 min read
What this means (non-technical)
Execution progress saving stores intermediate steps while a workflow is running. This stores intermediate state during execution, which can affect how workflow interruptions are handled depending on configuration, but it also increases database writes during execution.
It adds overhead to every run.
What usually goes wrong
When enabled on high-frequency workflows:
Database load increases.
Execution speed decreases slightly.
Storage usage grows faster.
Performance may degrade over time.
It can be helpful in specific cases, but leaving it on everywhere can quietly slow your system.
You may notice the system feels heavier without understanding why.
When this becomes urgent
This becomes urgent when:
Workflows run frequently.
Database performance is declining.
Storage costs increase.
You scale to higher volumes.
The more executions you run, the more overhead progress saving adds.
Detect issues in your n8n workflows
|
Definitions
Execution progress saving: Storing workflow state during execution so it can potentially resume after failure.
Database overhead: Additional load caused by extra read/write operations.
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.