langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-23 13:05:55 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

cloud.dify.ai conversation records error #6668

New Issue
Closed
opened 2026-02-21 18:16:46 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:16:46 -05:00
Owner
Copy Link
Copy Source

Originally created by @ouni3 on GitHub (Nov 11, 2024).

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.11.0

Cloud or Self Hosted

Cloud

Steps to reproduce

On cloud.dify.ai, I logged in with the same account, but the account ID is different from the one I had a few days ago, and I am unable to retrieve the conversation records from the previous days.I accessed the bot using my phone and incognito mode and got different chat records, which means the account ID doesn't rely on the Dify account, but on the device, so once the device status changes, the account ID also changes, making it impossible to retrieve previous chat records
image

✔️ Expected Behavior

When the same account logs into the robot chat interface from a different device, it should have the same chat history.

❌ Actual Behavior

I logged in with the same account, but the account ID is different from the one I had a few days ago, and I am unable to retrieve the conversation records from the previous days.

Originally created by @ouni3 on GitHub (Nov 11, 2024). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.11.0 ### Cloud or Self Hosted Cloud ### Steps to reproduce On cloud.dify.ai, I logged in with the same account, but the account ID is different from the one I had a few days ago, and I am unable to retrieve the conversation records from the previous days.I accessed the bot using my phone and incognito mode and got different chat records, which means the account ID doesn't rely on the Dify account, but on the device, so once the device status changes, the account ID also changes, making it impossible to retrieve previous chat records ![image](https://github.com/user-attachments/assets/8281b1ba-f807-4fcb-af3e-92326298aa5d) ### ✔️ Expected Behavior When the same account logs into the robot chat interface from a different device, it should have the same chat history. ### ❌ Actual Behavior I logged in with the same account, but the account ID is different from the one I had a few days ago, and I am unable to retrieve the conversation records from the previous days.
yindo added the 🐞 bug label 2026-02-21 18:16:46 -05:00
yindo closed this issue 2026-02-21 18:16:46 -05:00
yindo commented 2026-02-21 18:16:46 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 11, 2024):

I found a similar unsolved discussion regarding issues with conversation IDs and memory in Dify. You might find it helpful to check out this discussion: i have problem with messages on conversationID. My agent does not have memory [1].

Regarding your issue, it seems like there might be a problem with how Dify handles account IDs and conversation history across different devices. Unfortunately, I couldn't find specific documentation or code that explains how Dify links conversation history to user accounts across different devices. This might be a limitation or a bug in the current version (0.11.0) of Dify. You might want to report this issue to the Dify team if it hasn't been addressed yet.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Nov 11, 2024): <!-- Answer --> I found a similar unsolved discussion regarding issues with conversation IDs and memory in Dify. You might find it helpful to check out this discussion: [i have problem with messages on conversationID. My agent does not have memory](https://github.com/langgenius/dify/discussions/8974) <sup>[[1]](https://github.com/langgenius/dify/discussions/8974)</sup>. Regarding your issue, it seems like there might be a problem with how Dify handles account IDs and conversation history across different devices. Unfortunately, I couldn't find specific documentation or code that explains how Dify links conversation history to user accounts across different devices. This might be a limitation or a bug in the current version (0.11.0) of Dify. You might want to report this issue to the Dify team if it hasn't been addressed yet. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:16:46 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 11, 2024):

This is an expected behavior, we do not have a place for chatbot login as well. So, no matter logged in or not, if you change to another browser or use open it in private mode, the conversation id will change for sure.

@crazywoola commented on GitHub (Nov 11, 2024): This is an expected behavior, we do not have a place for chatbot login as well. So, no matter logged in or not, if you change to another browser or use open it in private mode, the conversation id will change for sure.
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 🐞 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#6668
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?