How to Clear Execution History in n8n: The Complete 2026 Guide

If you have been running automations for more than a week, you have likely noticed that n8n is a bit of a digital packrat. It loves to save every single detail of every single execution. While this is fantastic for debugging, it can quickly turn into a storage nightmare. Learning how to Clear Execution History in n8n is not just a cleaning task; it is a vital performance optimization strategy for 2026. 🚀

Why Your Database Needs a Detox 🧹

Imagine your n8n instance as a high-speed library. Every time a workflow runs, the librarian (n8n) writes a detailed report and stuffs it into a filing cabinet (your database). If you run 10,000 workflows a day, that filing cabinet is going to explode. Clearing execution history in n8n prevents this digital bloat from slowing down your interface.

In 2026, with the advent of high-frequency AI nodes, the data generated per execution has increased significantly. Large JSON objects and binary data can eat up gigabytes of space in hours. A bloated database leads to sluggish node response times, failing backups, and eventually, the dreaded “Out of Disk Space” error. 📉

Think of it like a backpack. A few pebbles (execution logs) are fine, but a thousand rocks will eventually stop you from moving. By learning to Clear Execution History in n8n, you keep your backpack light and your automation hikes effortless.

The Manual Scrub: UI Method 🖱️

For those who prefer a hands-on approach, n8n provides a straightforward way to delete history directly from the dashboard. This is perfect for one-off cleanups after a massive testing session. You can navigate to the “Executions” tab on the left-hand sidebar to see your list of past runs.

From here, you can filter by “Success” or “Error” and select specific items to delete. However, clicking “Delete” on 50,000 records manually is a recipe for carpal tunnel syndrome. For bulk actions, you can use the “Select All” feature, but be warned: this can momentarily freeze your browser if the list is too long. ⚠️

Manual clearing is the “emergency brake” of history management. It is great when you’ve accidentally looped a workflow 10,000 times, but it is not a sustainable long-term solution. For that, we need to look at the engine under the hood.

The Set-and-Forget: Environment Variables ⚙️

This is where the real magic happens. n8n comes with a built-in “janitor” that can automatically Clear Execution History in n8n based on rules you define. These are set via environment variables on your server or Docker container. It is the most robust way to maintain a healthy instance without lifting a finger.

The primary variable is EXECUTIONS_DATA_PRUNING. When set to true, n8n will periodically delete old records. You can then specify how many hours to keep data using EXECUTIONS_DATA_MAX_AGE. For example, setting it to 168 hours keeps exactly one week of history. 🗓️

Another powerful setting is EXECUTIONS_DATA_PRUNING_MAX_COUNT, which caps the total number of executions stored regardless of age. This is like a “one in, one out” policy at a trendy nightclub. It ensures your database never exceeds a certain size, which is critical for small VPS setups.

Cleanup Methods Compared 📊

Choosing the right way to Clear Execution History in n8n depends on your specific needs. Here is a quick breakdown of the common methods available in 2026.

Method	Speed	Automation Level	Best For…
UI Manual Delete	Slow	Manual	Testing & Small Cleanups
Env Variables (Pruning)	Instant	Full Auto	Production Instances
Database SQL Commands	Fast	Manual/Scripted	Advanced Power Users
CLI Maintenance	Medium	Semi-Auto	Server Administrators

Pro Code: Maintenance Workflow 💻

Sometimes you want more granular control than environment variables allow. You might want to keep “Error” logs for 30 days but delete “Success” logs after 2 hours. In 2026, we do this using a Maintenance Workflow. You can use a Code Node to interact with the n8n database or use the n8n API itself.

The following JavaScript snippet can be used inside a Code Node to identify high-volume workflows that might be candidates for aggressive clearing. Think of this script as a “Storage Audit” tool for your automation suite.

// n8n Storage Audit Script v2026.1
// This script simulates a check on execution data size per workflow
// It helps identify which workflows are the 'storage hogs'

const workflows = $input.all();
const thresholdMB = 100; // Define your 'danger zone' threshold

const auditResults = workflows.map(item => {
    // We assume the input contains workflow execution stats
    const size = item.json.storageUsedMB || 0; 
    
    return {
        json: {
            workflowName: item.json.name,
            currentSize: size + "MB",
            needsClearing: size > thresholdMB,
            actionRecommended: size > thresholdMB ? "ENABLE AGGRESSIVE PRUNING" : "KEEP AS IS"
        }
    };
});

// Logic explanation: 
// We iterate through our workflows and flag any that exceed 100MB of history.
// This allows us to target our 'Clear Execution History in n8n' efforts precisely.
return auditResults;

This code acts like a smart thermometer for your database. Instead of guessing which workflow is causing the bloat, you get a clear list of offenders. You can then use the n8n API nodes to trigger deletions for those specific IDs, keeping your important logs safe while vaporizing the junk. 🔍

The Highs and Lows of Clearing History ✅❌

Pros

• Lightning Speed: A smaller database means faster UI loading and quicker node execution. ⚡
• Lower Costs: Reduced storage requirements mean cheaper server hosting bills. 💸
• Better Backups: Smaller databases are significantly faster to back up and restore during disasters.
• Data Privacy: Automatically clearing old data helps comply with GDPR and other data retention policies.

Cons

• No Rewind: Once you Clear Execution History in n8n, that data is gone forever. No “Undo” button exists. 🚫
• Debugging Difficulty: If a workflow failed 8 days ago and you prune every 7 days, you lose the evidence.
• Audit Trails: Some industries require 90+ days of logs for compliance, which conflicts with aggressive pruning.

Pro Tips for 2026 💡

1. **Selective Success Saving:** In your workflow settings, you can toggle “Save Successful Executions” to “Off”. This is the ultimate way to Clear Execution History in n8n—by never creating it in the first place! For high-frequency “helper” workflows, this is a must.

2. **External Logging:** If you need to keep data for compliance but want a fast n8n, send your execution data to an external log manager like Axiom or BetterStack. This keeps n8n lean while preserving the data elsewhere. 🌐

3. **Monitor Disk Space:** Use a system monitoring tool to alert you when your disk hits 80%. Don’t wait for n8n to crash to realize your execution history has grown too large.

4. **Vacuum Your Database:** If you use PostgreSQL, deleting records doesn’t always reclaim space immediately. Periodically run a `VACUUM` command to tell the database to actually shrink the file size on the disk. 🧹

How to Use It Properly: A Workflow Strategy 🛠️

To Clear Execution History in n8n effectively, you should adopt a tiered strategy. Start by setting your global environment variables to a “safe” default, like 14 days. This provides a safety net for all workflows.

Next, identify your “noisy” workflows—the ones that run every minute. For these, manually go into their settings and disable saving successful executions. This prevents the “Success” logs from even entering your database, which is the most efficient form of cleanup.

Finally, for mission-critical workflows, use the n8n API to move execution data to a cheap storage bucket (like S3) before the pruning script deletes them. This “Cold Storage” approach gives you the best of both worlds: a fast n8n instance and a permanent audit trail. 🧊

Frequently Asked Questions ❓

Q: Does clearing history delete my workflows?
A: No! Clearing history only removes the “logs” of what happened. Your actual workflow designs (the nodes and connections) remain perfectly safe. 🛡️

Q: How often does the automatic pruning run?
A: By default, n8n runs its pruning task every hour. You can adjust this frequency in the configuration if you have extremely high data throughput.

Q: Can I clear history for just one specific workflow?
A: Yes. In the workflow settings (the gear icon), you can override the global pruning settings to be more or less aggressive for that specific workflow.

Q: Why is my database still big after deleting history?
A: Databases like SQLite and PostgreSQL often keep “empty space” reserved for future data. You may need to perform a database compression or “VACUUM” to see the file size decrease. 📦

Managing your data is an essential part of being a senior automation engineer. For more advanced technical deep-dives, check out the official n8n documentation on environment variables.

Ready to take your automation skills to the next level? Explore more guides and tutorials at n8nnode.com.