Question
Is anyone finding themselves using loops around agents to better handling memory management, particularly when using simple memory? I find I start running into browser memory issues on longer runs and have to put this awkward loop in to ensure it’s getting cleared between iterations. Obviously only useful if it can be naturally cleared between iterations.
It would be nice if the Simple Memory supported this as an option.
What is the error message (if any)?
Please share your workflow
Mostly wondering if I’m overthinking this or if someone has found a more eloquent way of handling this?
Hey @brendan6 ,
Just to clarify…in n8n, Simple Memory is really meant only for testing and development purposes. It stores all the conversation data in your browser’s memory, so naturally, over longer runs it can cause memory issues like you’re experiencing.
To avoid this, it’s better to use other memory options n8n offers. The easiest and best one to use is PostgreSQL Memory. It stores data outside your browser, so it won’t cause those memory issues.
There are many videos on YouTube that show how to set it up. If you want, I can explain how to do it here too!
This way, you don’t need to use loops or tricks to clear memory…it will just work better.