AgentFlows Chatbot Showing Old Conversations Mid-Session (Context Reset / Glitch)

[Kushiqtx]

Hi, I'm building a chatbot using Flowise AgentFlows, and I’m facing a recurring issue where the chatbot suddenly shows older chat messages and responses from previous sessions, even after clearing the session.

The problem occurs mid-conversation:

I ask a new question

AgentFlows starts processing

Suddenly, the UI displays old chat logs from a previous run

Or it mixes old responses with the current one

It seems like the internal memory / session store is leaking or not resetting reliably.

flowise_ambient.mp4

[Ganesh-403]

@Kushiqtx
What you're describing doesn't sound like expected AgentFlows behavior. A cleared or new session should not suddenly rehydrate messages from an unrelated conversation midway through processing.

From what I can tell, this is likely one of three things:

1. The same sessionId (or chatId) is being reused, so the agent is loading existing conversation history.
2. Memory is backed by a persistent store (Redis, database, etc.) that isn't being cleared when you think it is.
3. A bug/regression in AgentFlows where the UI or memory layer is restoring stale messages.

Things to check

1. Verify you're creating a new session

If you're calling the Prediction API yourself, ensure each new conversation uses a unique sessionId (and chatId if applicable). Reusing these identifiers will intentionally associate the request with the previous conversation history. Flowise uses session identifiers to maintain conversational state. :contentReference[oaicite:0]{index=0}

2. Check the memory configuration

If your Agent node has memory enabled (Buffer Memory, Redis Memory, etc.), verify:

• the correct session key is being used,
• memory is actually cleared when starting a new conversation,
• no external persistence layer is restoring old messages.

A mismatch between the UI session and the memory session is a common cause of "old conversations" appearing unexpectedly.

3. Determine whether it's a UI or backend issue

A useful test is to inspect the execution trace or the API response:

• If the API response already contains old messages, the issue is likely in the backend/memory.
• If the API response is correct but the UI suddenly displays previous messages, the problem is more likely in the frontend state management.

This helps narrow down where the stale context is being introduced.

4. Test with memory disabled

As a quick isolation step:

• disable memory on the Agent,
• start a completely new session,
• see if the issue still occurs.

If the problem disappears, it's strong evidence that the memory/session layer is involved rather than the AgentFlow execution itself.

If this is reproducible...

If you're consistently seeing previous conversations injected into a brand-new session—even with unique session IDs—that would point to a probable AgentFlows bug rather than expected behavior.

To help reproduce it, it would be useful to share:

• Flowise version
• Self-hosted or Cloud
• Memory type (Buffer, Redis, Database, etc.)
• Whether you're using the built-in chat UI or the Prediction API
• Whether every new conversation gets a fresh sessionId/chatId
• Whether the stale messages appear in the API response or only in the UI

Those details should make it much easier to determine whether this is a configuration issue or a regression in AgentFlows.

If this solves your problem, feel free to mark it as the accepted answer so others can find it easily.