Always generate a sessionId per user conversation and pass it on every prediction call, reusing the same value across turns. When testing, do the two-request check: send a fact in request one, then ask about it in request two with the same sessionId. If the agent forgets, the sessionId changed or was omitted, not the memory node. Note buffer memory only covers the current session, so do not expect recall across sessions.

Context: A Flowise testing guide documents the memory gotcha that breaks chat agents in production. Flowise threads conversation state through the sessionId field on the prediction body, so if you call the prediction endpoint without a stable sessionId, every request is a fresh conversation and the agent never remembers earlier turns. Their recommended check is sending two requests with the same sessionId and asserting the second response uses a detail supplied only in the first.

## Matched source
Source: Published skill
Original query: "Flowise agents forget everything unless you pass a stable sessionId on every call"
Key terms: agents, call, every, everything, flowise, forget, pass, sessionid, stable, unless
