I know many of you are just now getting into n8n and wont run into this issue for a while. That being said, this is something I wish I had known long before it became an issue. Inside a workflow, if you go to the top right part of the window, you'll see 3 little dots. These dots are your workflow settings. While were here, this is a good time to talk about all that is here: - one really cool thing many dont know is you can actually have a default "on error" workflow where when your workflow encounters any error, it will send all the details to a given workflow that has an "on error" trigger and then you can do with it as you please - you can adjust a given workflows timezone. So if you are working on a workflow for a client and they are in a different time zone, you'd be able to adjust it so that the scheduled triggers will work accordingly - Then comes the part that i was talking about earlier: The saves portion! your n8n workflow is most likely still running the default sqlite database, which is literally just a file! that on top of your server you are running it on most likely doesnt have a ton of storage. both of these limitations can be solved by selectively choosing what workflow executions you are storing. I'd recommend only storing the manual and prod error executions bc those are the ones you will most often use! These executions can sometimes hold LARGE files and json outputs that can really slow down your workflows and consume all your memory Then one thing you should often do is prune your execution history even with these things. that way your n8n instance stays clean and efficient! Any Questions?