Uploaded August 2026 | Updated September 2026, 2 weeks ago
Welcome back to another critical, server-saving episode in our massive n8n workflow automation series! When you are building and testing complex automations in n8n, you spend a lot of time clicking the "Execute Workflow" button manually. By default, n8n handles the logs for manual executions differently than production executions to save space, but what if you need to keep those test logs for debugging? Or, conversely, what if your database is overflowing with thousands of saved manual runs and you need to bulk-delete them? In this fully updated 2026 comprehensive tech tutorial, we are going to show you exactly how to save or unsave all manual executions in n8n, manage your workspace settings, and optimize your database!
In the first section of this complete video guide, we will tackle the Workspace Settings interface! We will walk you through exactly how to navigate to your global settings and locate the Execution Data management toggles. You will learn the crucial difference between "Save Data for Successful Executions" and "Save Data for Manual Executions." We will show you how flipping the toggle to "Save" allows you to preserve the JSON payload and routing history of every single test run—an absolute lifesaver when you are trying to debug a complex API connection that only fails during manual testing!
Next, we take a deep dive into bulk management and clearing out old data. If you have been saving manual executions for months, your n8n database (SQLite or Postgres) might be getting bloated, slowing down your server! We will show you how to navigate to the Executions tab and use the bulk selection tools to delete thousands of saved manual executions at once. We will also demonstrate how to turn the manual save feature back OFF once you are finished developing, ensuring your production server remains clean and lightning-fast.
Moving into the second half of our tutorial, we explore advanced execution management for self-hosters via Docker. We will open up our `docker-compose.yml` file and show you the exact environment variables used to automate this process globally! You will learn how to configure `EXECUTIONS_DATA_SAVE_ON_SUCCESS`, `EXECUTIONS_DATA_SAVE_ON_ERROR`, and specifically `EXECUTIONS_DATA_SAVE_MANUAL_EXECUTIONS`. We will show you how setting these variables at the container level guarantees that your entire team follows the same logging rules, preventing database bloat automatically!
Mastering how to save, unsave, and manage your manual execution logs in n8n is the ultimate key to developing efficiently while keeping your self-hosted server optimized and crash-free!
Thank you so much for tuning in to this complete n8n execution data tutorial! If this 2026 tech guide helped you clean up your bloated database or finally save that crucial test log today, please make sure to smash that like button and share this video with a fellow developer or operations manager who self-hosts n8n! Subscribe to the channel and turn on the notification bell so you never miss out on our upcoming n8n tutorials, AI agent builds, and Docker optimization guides. Drop a comment down below letting us know if you prefer to save or discard your manual test runs, and we will see you in the next video!
#n8n #n8nTutorial #WorkflowAutomation #ExecutionLogs #DataManagement #ZapierAlternative #MakeAlternative #TechTutorial2026 #DockerTutorial #OpenSource #SelfHosted #DevOps
youtube tags:
how to save manual executions n8n,n8n unsave manual executions,n8n execution logs,n8n clear execution history,n8n save data for manual executions,n8n database bloat,n8n tutorial 2026,n8n environment variables,docker compose n8n execution data,zapier alternative,make.com alternative,workflow automation,open source automation,self hosted n8n,n8n troubleshoot,n8n performance optimization,delete executions n8n,n8n executions_data_save_manual_executions,no code debugging,automate business processes
```eof
Welcome back to another critical, server-saving episode in our massive n8n workflow automation series! When you are building and testing complex automations in n8n, you spend a lot of time clicking the "Execute Workflow" button manually. By default, n8n handles the logs for manual executions differently than production executions to save space, but what if you need to keep those test logs for debugging? Or, conversely, what if your database is overflowing with thousands of saved manual runs and you need to bulk-delete them? In this fully updated 2026 comprehensive tech tutorial, we are going to show you exactly how to save or unsave all manual executions in n8n, manage your workspace settings, and optimize your database!
In the first section of this complete video guide, we will tackle the Workspace Settings interface! We will walk you through exactly how to navigate to your global settings and locate the Execution Data management toggles. You will learn the crucial difference between "Save Data for Successful Executions" and "Save Data for Manual Executions." We will show you how flipping the toggle to "Save" allows you to preserve the JSON payload and routing history of every single test run—an absolute lifesaver when you are trying to debug a complex API connection that only fails during manual testing!
Next, we take a deep dive into bulk management and clearing out old data. If you have been saving manual executions for months, your n8n database (SQLite or Postgres) might be getting bloated, slowing down your server! We will show you how to navigate to the Executions tab and use the bulk selection tools to delete thousands of saved manual executions at once. We will also demonstrate how to turn the manual save feature back OFF once you are finished developing, ensuring your production server remains clean and lightning-fast.
Moving into the second half of our tutorial, we explore advanced execution management for self-hosters via Docker. We will open up our `docker-compose.yml` file and show you the exact environment variables used to automate this process globally! You will learn how to configure `EXECUTIONS_DATA_SAVE_ON_SUCCESS`, `EXECUTIONS_DATA_SAVE_ON_ERROR`, and specifically `EXECUTIONS_DATA_SAVE_MANUAL_EXECUTIONS`. We will show you how setting these variables at the container level guarantees that your entire team follows the same logging rules, preventing database bloat automatically!
Mastering how to save, unsave, and manage your manual execution logs in n8n is the ultimate key to developing efficiently while keeping your self-hosted server optimized and crash-free!
Thank you so much for tuning in to this complete n8n execution data tutorial! If this 2026 tech guide helped you clean up your bloated database or finally save that crucial test log today, please make sure to smash that like button and share this video with a fellow developer or operations manager who self-hosts n8n! Subscribe to the channel and turn on the notification bell so you never miss out on our upcoming n8n tutorials, AI agent builds, and Docker optimization guides. Drop a comment down below letting us know if you prefer to save or discard your manual test runs, and we will see you in the next video!
#n8n #n8nTutorial #WorkflowAutomation #ExecutionLogs #DataManagement #ZapierAlternative #MakeAlternative #TechTutorial2026 #DockerTutorial #OpenSource #SelfHosted #DevOps
youtube tags:
how to save manual executions n8n,n8n unsave manual executions,n8n execution logs,n8n clear execution history,n8n save data for manual executions,n8n database bloat,n8n tutorial 2026,n8n environment variables,docker compose n8n execution data,zapier alternative,make.com alternative,workflow automation,open source automation,self hosted n8n,n8n troubleshoot,n8n performance optimization,delete executions n8n,n8n executions_data_save_manual_executions,no code debugging,automate business processes
```eof
