langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-19 08:35:20 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

The chat assistant for the browser with dual windows reported an error: "Conversation Does Not Exist." #20151

New Issue
Closed
opened 2026-02-21 20:06:04 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:06:04 -05:00
Owner
Copy Link
Copy Source

Originally created by @jackqlliu on GitHub (Nov 5, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.7.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

If different chat assistant agents are opened through embedding the website in the browser, an error message "Conversation Not Exists" will be displayed.

✔️ Expected Behavior

Each chat assistant uses its own token.

❌ Actual Behavior

The chat assistants all invoked the passport interface to generate new tokens, but they kept reporting the error "Conversation Does Not Exist".

Image Image
Originally created by @jackqlliu on GitHub (Nov 5, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.7.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce If different chat assistant agents are opened through embedding the website in the browser, an error message "Conversation Not Exists" will be displayed. ### ✔️ Expected Behavior Each chat assistant uses its own token. ### ❌ Actual Behavior The chat assistants all invoked the passport interface to generate new tokens, but they kept reporting the error "Conversation Does Not Exist". <img width="2232" height="596" alt="Image" src="https://github.com/user-attachments/assets/2799eb4d-869d-4f1b-853b-23893aa7b071" /> <img width="2948" height="992" alt="Image" src="https://github.com/user-attachments/assets/b2dfec4a-995b-48a4-8960-8faebbd489c8" />
yindo added the 🐞 bugoutdated labels 2026-02-21 20:06:04 -05:00
yindo closed this issue 2026-02-21 20:06:04 -05:00
yindo commented 2026-02-21 20:06:04 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 5, 2025):

This is a known bug in Dify v1.7.0 (self-hosted, Docker) when embedding multiple chat assistants in the browser: even though each assistant generates a new token via the passport interface, they can end up sharing or overwriting session and conversation context, leading to the "Conversation Does Not Exist" error. This happens because session IDs and tokens are not properly isolated per assistant instance—if multiple assistants share the same session or localStorage context, their conversations collide and break context tracking.

Recent updates (after v1.7.0) have refactored token management to use HTTP-only cookies instead of localStorage, which may help with session isolation in future releases, but this does not fully resolve the issue if each embedded assistant does not have a unique user/session identity per window or tab cite.

Workarounds:

  • Make sure each embedded assistant instance is initialized with a unique user/session ID.
  • If you are switching users or contexts, reload the iframe and clear browser storage to avoid session collisions cite.
  • Always use the conversation_id and user/session_id exactly as returned by the API—do not generate custom IDs or mix API/UI-created conversations cite.

This bug is tracked in issue #27869. If you need a robust fix, monitor that thread and consider upgrading to a version with the new token management system once available. For now, focus on ensuring per-instance session isolation in your embedding logic.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 5, 2025): <!-- Answer --> This is a known bug in Dify v1.7.0 (self-hosted, Docker) when embedding multiple chat assistants in the browser: even though each assistant generates a new token via the passport interface, they can end up sharing or overwriting session and conversation context, leading to the "Conversation Does Not Exist" error. This happens because session IDs and tokens are not properly isolated per assistant instance—if multiple assistants share the same session or localStorage context, their conversations collide and break context tracking. Recent updates (after v1.7.0) have refactored token management to use HTTP-only cookies instead of localStorage, which may help with session isolation in future releases, but this does not fully resolve the issue if each embedded assistant does not have a unique user/session identity per window or tab [cite](https://github.com/langgenius/dify/pull/24365). Workarounds: - Make sure each embedded assistant instance is initialized with a unique user/session ID. - If you are switching users or contexts, reload the iframe and clear browser storage to avoid session collisions [cite](https://github.com/langgenius/dify/issues/25768). - Always use the conversation_id and user/session_id exactly as returned by the API—do not generate custom IDs or mix API/UI-created conversations [cite](https://github.com/langgenius/dify/issues/20149). This bug is tracked in [issue #27869](https://github.com/langgenius/dify/issues/27869). If you need a robust fix, monitor that thread and consider upgrading to a version with the new token management system once available. For now, focus on ensuring per-instance session isolation in your embedding logic. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/5969edb3-8977-4b92-b2cb-7a586f855e3a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5969edb3-8977-4b92-b2cb-7a586f855e3a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5969edb3-8977-4b92-b2cb-7a586f855e3a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5969edb3-8977-4b92-b2cb-7a586f855e3a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5969edb3-8977-4b92-b2cb-7a586f855e3a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5969edb3-8977-4b92-b2cb-7a586f855e3a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5969edb3-8977-4b92-b2cb-7a586f855e3a?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/27869)
yindo commented 2026-02-21 20:06:04 -05:00
Author
Owner
Copy Link
Copy Source

@jackqlliu commented on GitHub (Nov 5, 2025):

Has the new version fixed this issue?

@jackqlliu commented on GitHub (Nov 5, 2025): Has the new version fixed this issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label outdated 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#20151
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?