Bug with SessionId, Simple Memory and Postgres Chat Memory on 1.121.3

Hello everyone, I’m having an issue with the latest version of n8n as of today (1.121.3). The problem is with the Simple Memory node, which—no matter what limit I set—always returns absolutely all the memory it has stored. But this doesn’t happen only with Simple Memory; it also happens with Postgres Chat Memory. I’ve also noticed that even when I reload the sessionId, it still remains the same. Am I the only one experiencing this?

Same here!
For now, every time you reset the chat session, you need to reload the tab for it to take effect, otherwise it will keep using the old sessionId..

I already tried it, thanks, but the issue with Postgres Chat Memory and Simple Memory is still there. I suspect this bug has been around since a previous version.

I think I’m having a similar issue. Simple Memory fills the agent with so much content that after chating for 15 min every simple request is requiring 100-200k tokens. What other options for memory should I be looking into? Is this a setup problem on my part? I’ve only been learning n8n for a few days..

It was fixed in v1.123.0

So you may need to update your version if you haven’t yet..