404,Conversation Not Exists. #11201

Closed
opened 2026-02-21 18:56:52 -05:00 by yindo · 0 comments
Owner

Originally created by @zhoujian3314 on GitHub (Mar 15, 2025).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I have deployed Dify locally and am trying to retrieve conversation history via the API. The user and conversation_id values are obtained from the Dify admin logs, so I am certain they are correct. However, when calling the /v1/messages API, it returns a 404 error with the message "Conversation Not Exists." Additionally, the /v1/conversations API returns an empty list, indicating no conversations exist for the user. Upon investigating the PostgreSQL database, I found that the from_end_user_id in the conversations table does not match the provided user ID, and the user ID I used matches the session_id in the end_users table, which seems incorrect and confusing.

Image
Image
Image
Image

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @zhoujian3314 on GitHub (Mar 15, 2025). ### 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.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I have deployed Dify locally and am trying to retrieve conversation history via the API. The user and conversation_id values are obtained from the Dify admin logs, so I am certain they are correct. However, when calling the /v1/messages API, it returns a 404 error with the message "Conversation Not Exists." Additionally, the /v1/conversations API returns an empty list, indicating no conversations exist for the user. Upon investigating the PostgreSQL database, I found that the from_end_user_id in the conversations table does not match the provided user ID, and the user ID I used matches the session_id in the end_users table, which seems incorrect and confusing. ![Image](https://github.com/user-attachments/assets/15c6b67c-cbfe-43b8-992d-7044d6567c81) ![Image](https://github.com/user-attachments/assets/f6e00ba4-cde3-43e1-90a7-d00c30c1e82a) ![Image](https://github.com/user-attachments/assets/9666478c-5e4b-4419-8175-6915a0045dbd) ![Image](https://github.com/user-attachments/assets/114bbdad-c1e0-4996-888e-590539a61847) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:56:52 -05:00
yindo closed this issue 2026-02-21 18:56:52 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#11201