Chat memories are not deleted when chat session is deleted

[jonepo]

Chat memories are not deleted when chat session is deleted

[tdechanterac]

I had the same issue, but are you sure it's not the long term memory that still exists ?
From what I understand from the documentation, this kind of memory should be always available.

[jonepo]

At least in this chat-copilot sample project, working and long-term memory are saved with the chat ID tag in the Kernel Memory. So they both are contained within a single conversation, which means there wouldn't be a point in keeping the long-term memory items when the conversation is deleted.

[dipteshbosedxc]

Same behaviour. The document persists in memory indefinitely. The RAG functionality is activated even with a new context (such as a new chat session) where the document hasn’t been uploaded. For instance, while my custom plugin operates correctly, it still references a PDF document for RAG purposes due to its retention in long-term memory.

[jonepo]

That sounds odd as I thought it always will set the chat session ID as the tag before saving it to the memory. That way it shouldn't return document chunks from other sessions as it filters with the current chat session ID. Maybe it's another bug.

[dipteshbosedxc]

You are correct. Seems like Chat Copilot app needs an upgrade. There is no way one can delete uploaded documents or clear the vector database => in this case TextFile

[jonepo]

Ah yes, you were talking about the global scoped documents. They indeed are kept there forever as the UI doesn't have the option to delete them. And as they are globally scoped, any chat session can use them as citations.

This issue I created is just related to the chat session scoped document, working, and long-term memory not being deleted when the session is deleted.

[Dikarabo-Molele]

I found that the snipped shared above prevented the system from deleting chat memory files in the storage account and did not remove embeddings in the vector store.

The value of the first item after the split is 'chatmemory' and not the document id

I fixed the issue by referencing DocumentId property instead of Link