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

conversaion not found #11753

Open
5 tasks done
lingfengchencn opened this issue Dec 17, 2024 · 1 comment
Open
5 tasks done

conversaion not found #11753

lingfengchencn opened this issue Dec 17, 2024 · 1 comment
Labels
🐞 bug Something isn't working

Comments

@lingfengchencn
Copy link
Contributor

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.14.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After upgrading from version 0.8.3 to 0.14.0, if you input something to chat with the app, you might receive a "conversation not found" error and it will open a new chat with no content. However, if you remove the local storage, the issue resolves and works fine.

✔️ Expected Behavior

if conversation id lost , just remove it or can open new conversations..

❌ Actual Behavior

tips: conversation not found
refresh page and can't open a new conversation .
keep here:
image

@dosubot dosubot bot added the 🐞 bug Something isn't working label Dec 17, 2024
Copy link

dosubot bot commented Dec 17, 2024

I found a similar unsolved discussion that might be relevant to your issue: How to Send a Conversation Message using "conversation_id", which was last updated on October 18, 2024 [1].

Regarding your issue, Dify handles conversation IDs by retrieving them from the variable_pool using the key ["sys", "conversation_id"]. If the conversation ID is not found, it raises a ConversationIDNotFoundError [2]. This might be related to the "conversation not found" error you're encountering.

Additionally, Dify uses local storage to manage conversation states and IDs. It employs the useLocalStorageState hook to store and retrieve conversationIdInfo, which helps persist conversation states across sessions [3]. Clearing the local storage seems to resolve the issue because it resets the stored conversation states, allowing the application to start fresh without the missing or corrupted conversation ID.

To address this issue, you might consider implementing a mechanism to automatically clear or reset the conversation ID in local storage when it is not found, which aligns with your expected behavior of opening new conversations if the ID is lost.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant