Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (Language Policy).
• Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• Please do not modify this template :) and fill in all the required fields.

RAGFlow workspace code commit ID

#11689

RAGFlow image version

v0.22.1

Other environment information

I found that when multiple users share the same agent simultaneously, there is no isolation mechanism. Especially, historical memories can be overwritten by subsequent requests. Is there a solution to this problem? Session-level isolation was found in canvas.pletion, but this isolation was not used in the /completion interface of Canvas_app?

Actual behavior

I found that when multiple users share the same agent simultaneously, there is no isolation mechanism. Especially, historical memories can be overwritten by subsequent requests. Is there a solution to this problem? Session-level isolation was found in canvas.pletion, but this isolation was not used in the /completion interface of Canvas_app?

Expected behavior

I found that when multiple users share the same agent simultaneously, there is no isolation mechanism. Especially, historical memories can be overwritten by subsequent requests. Is there a solution to this problem? Session-level isolation was found in canvas.pletion, but this isolation was not used in the /completion interface of Canvas_app?

Steps to reproduce

I found that when multiple users share the same agent simultaneously, there is no isolation mechanism. Especially, historical memories can be overwritten by subsequent requests. Is there a solution to this problem? Session-level isolation was found in canvas.pletion, but this isolation was not used in the /completion interface of Canvas_app?

Additional information

No response