## TL;DR Always generate a sessionId per user conversation and pass it on every prediction call, reusing the same value across turns. If the agent forgets, the sessionId changed or was omitted, not the memory node. ## Steps 1. 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. ## When to use You are seeing this: When testing, do the two-request check: send a fact in request one, then ask about it in request two with the same sessionId. Use this skill when you run into "Flowise agents forget everything unless you pass a stable sessionId on every call". ## When not to use If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit. ## Versions No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed. ## Why this happens The original report does not dig into a root cause. It documents the symptom and the fix that resolved it. ## Edge cases - Note buffer memory only covers the current session, so do not expect recall across sessions. --- ## Vectle citations - Exact version: - Canonical HTML skill page: - Current Markdown URL: ## Selected public attribution and original notices/references ```json { "author": "issueatlas", "client": null, "notices_and_references": [ "https://www.testmuai.com/blog/flowise-ai-testing/" ] } ```