Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintain Session ID to differentiate conversations between each user #885

Closed
vijaykammili opened this issue Sep 6, 2023 · 4 comments
Closed

Comments

@vijaykammili
Copy link
Contributor

I have the following flow that works well for one user at a time but not multiple users at once. How can i pass a sessionID to this flow and maintain each user's session? I know we can use Zep memory for other use cases. What are the options in this case?

image

@chungyau97
Copy link
Contributor

This PR will be what you're looking for #715, currently awaiting completions in this sequence #873 > #843 > #715

@vijaykammili
Copy link
Contributor Author

Thank you @chungyau97 for the quick response. Are you able to provide a timeline? I'm assuming this will fix two users not receiving responses for each other's questions? (It didn't seem clear from the other PRs so I wanted to clarify).

Currently if we make a call via API for user A with question a and another API call with User B with question b, User A is getting responses for User B and vice versa. Let me know. Great work btw!

@chungyau97
Copy link
Contributor

Hi @vijaykammili,

You have no other options beside using Zep Memory or alternative memory like Motorhead Memory.
Finally, you will need to provide a unique sessionId for each users in your API request.
image

This PR #715, will create a unique sessionId. Hopefully, I can complete it before this 3 PRs [#873 > #843 > #715] before October starts.

@vijaykammili
Copy link
Contributor Author

Thank you, again @chungyau97!

JohnBQuinn pushed a commit to JohnBQuinn/Flowise that referenced this issue Jun 7, 2024
* perf: insert mongo dataset data session

* perf: dataset data index

* remove delay

* rename bill schema

* rename bill record

* perf: bill table

* perf: prompt

* perf: sub plan

* change the usage count

* feat: usage bill

* publish usages

* doc

* 新增团队聊天功能 (FlowiseAI#20)

* perf: doc

* feat 添加标签部分

feat 信息团队标签配置

feat 新增团队同步管理

feat team分享页面

feat 完成team分享页面

feat 实现模糊搜索

style 格式化

fix 修复迷糊匹配

style 样式修改

fix 团队标签功能修复

* fix 修复鉴权功能

* merge 合并代码

* fix 修复引用错误

* fix 修复pr问题

* fix 修复ts格式问题

---------

Co-authored-by: archer <545436317@qq.com>
Co-authored-by: liuxingwan <liuxingwan.lxw@alibaba-inc.com>

* update extra plan

* fix: ts

* format

* perf: bill field

* feat: standard plan

* fix: ts

* feat 个人账号页面修改 (FlowiseAI#22)

* feat 添加标签部分

feat 信息团队标签配置

feat 新增团队同步管理

feat team分享页面

feat 完成team分享页面

feat 实现模糊搜索

style 格式化

fix 修复迷糊匹配

style 样式修改

fix 团队标签功能修复

* fix 修复鉴权功能

* merge 合并代码

* fix 修复引用错误

* fix 修复pr问题

* fix 修复ts格式问题

* feat 修改个人账号页

---------

Co-authored-by: liuxingwan <liuxingwan.lxw@alibaba-inc.com>

* fix chunk index; error page text

* feat: dataset process Integral prediction

* feat: stand plan field

* feat: sub plan limit

* perf: index

* query extension

* perf: share link push app name

* perf: plan point unit

* perf: get sub plan

* perf: account page

---------

Co-authored-by: yst <77910600+yu-and-liu@users.noreply.github.com>
Co-authored-by: liuxingwan <liuxingwan.lxw@alibaba-inc.com>
JohnBQuinn pushed a commit to JohnBQuinn/Flowise that referenced this issue Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants