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

Conversation Not Exists Bug on Cloud #20461

New Issue
Closed
opened 2026-02-21 20:07:32 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 20:07:32 -05:00
Owner
Copy Link
Copy Source

Originally created by @juniorsereno on GitHub (Nov 20, 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.10.0

Cloud or Self Hosted

Cloud

Steps to reproduce

When send a message via http request receive this error 404 - "{"code":"not_found","message":"Conversation Not Exists. You have requested this URI [\/v1\/chat-messages] but did you mean \/v1\/chat-messages or \/api\/chat-messages or \/v1\/chat-messages\/string:task_id\/stop ?","status":404} at the second message with the user.

On the history the conversation exist and it's identic.

✔️ Expected Behavior

Expected the response. Cant't debug on dify because the message don't come in.

❌ Actual Behavior

404 - "{"code":"not_found","message":"Conversation Not Exists. You have requested this URI [\/v1\/chat-messages] but did you mean \/v1\/chat-messages or \/api\/chat-messages or \/v1\/chat-messages\/string:task_id\/stop ?","status":404}

Originally created by @juniorsereno on GitHub (Nov 20, 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.10.0 ### Cloud or Self Hosted Cloud ### Steps to reproduce When send a message via http request receive this error 404 - "{\"code\":\"not_found\",\"message\":\"Conversation Not Exists. You have requested this URI [\\/v1\\/chat-messages] but did you mean \\/v1\\/chat-messages or \\/api\\/chat-messages or \\/v1\\/chat-messages\\/<string:task_id>\\/stop ?\",\"status\":404} at the second message with the user. On the history the conversation exist and it's identic. ### ✔️ Expected Behavior Expected the response. Cant't debug on dify because the message don't come in. ### ❌ Actual Behavior 404 - "{\"code\":\"not_found\",\"message\":\"Conversation Not Exists. You have requested this URI [\\/v1\\/chat-messages] but did you mean \\/v1\\/chat-messages or \\/api\\/chat-messages or \\/v1\\/chat-messages\\/<string:task_id>\\/stop ?\",\"status\":404}
yindo added the 🐞 bugcloud labels 2026-02-21 20:07:32 -05:00
yindo closed this issue 2026-02-21 20:07:32 -05:00
yindo commented 2026-02-21 20:07:32 -05:00
Author
Owner
Copy Link
Copy Source

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

This 404 error usually means the API can't find a conversation that matches both the conversation_id and the user you provided. The most common causes are: the user parameter doesn't match the original creator of the conversation, a custom or manually generated conversation_id is used instead of the one returned by the API, or the conversation was created in the Web UI (console context) and not via the API (service_api context)—these are strictly separated and not cross-accessible citation.

Another known cause is sending the second message too quickly (e.g., within 500ms) after the first, before the conversation_id is fully registered in the backend database, which can lead to this error citation. Also, concurrent requests with the same app_key and user can create multiple end_user records, resulting in mismatched conversation ownership citation.

To avoid this: always use the exact conversation_id returned by the API, ensure the user parameter is consistent (lowercase, alphanumeric, no spaces), and add a short delay between the first and second requests. Only conversations started via the API with the correct user/session can be accessed through the API citation.

If you need to access conversations created in the Web UI via the API, that's not supported by design. If the problem persists even when following these rules, double-check that the user and conversation_id pair in your request matches exactly what was returned by the API when the conversation was created.

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 20, 2025): <!-- Answer --> This 404 error usually means the API can't find a conversation that matches both the conversation_id and the user you provided. The most common causes are: the user parameter doesn't match the original creator of the conversation, a custom or manually generated conversation_id is used instead of the one returned by the API, or the conversation was created in the Web UI (console context) and not via the API (service_api context)—these are strictly separated and not cross-accessible [citation](https://github.com/langgenius/dify/issues/22537). Another known cause is sending the second message too quickly (e.g., within 500ms) after the first, before the conversation_id is fully registered in the backend database, which can lead to this error [citation](https://github.com/langgenius/dify/issues/14893). Also, concurrent requests with the same app_key and user can create multiple end_user records, resulting in mismatched conversation ownership [citation](https://github.com/langgenius/dify/issues/15935). To avoid this: always use the exact conversation_id returned by the API, ensure the user parameter is consistent (lowercase, alphanumeric, no spaces), and add a short delay between the first and second requests. Only conversations started via the API with the correct user/session can be accessed through the API [citation](https://github.com/langgenius/dify/issues/20149). If you need to access conversations created in the Web UI via the API, that's not supported by design. If the problem persists even when following these rules, double-check that the user and conversation_id pair in your request matches exactly what was returned by the API when the conversation was created. <!-- 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/13762706-702f-4cb2-a492-3168ccef6bcb?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/13762706-702f-4cb2-a492-3168ccef6bcb?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/13762706-702f-4cb2-a492-3168ccef6bcb?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/13762706-702f-4cb2-a492-3168ccef6bcb?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/13762706-702f-4cb2-a492-3168ccef6bcb?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/13762706-702f-4cb2-a492-3168ccef6bcb?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/13762706-702f-4cb2-a492-3168ccef6bcb?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/28481)
yindo commented 2026-02-21 20:07:32 -05:00
Author
Owner
Copy Link
Copy Source

@me0106 commented on GitHub (Nov 25, 2025):

fix with https://github.com/langgenius/dify/pull/28462

@me0106 commented on GitHub (Nov 25, 2025): fix with https://github.com/langgenius/dify/pull/28462
yindo commented 2026-02-21 20:07:32 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 27, 2025):

Hi, @juniorsereno. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a 404 "Conversation Not Exists" error when sending a second HTTP message in Dify v1.10.0 Cloud.
  • The error was linked to mismatched user or conversation_id, UI vs API conversation access, or timing of the second message.
  • I implemented a fix in PR #28462 to resolve this specific issue.
  • The issue is considered resolved with the merged fix.

Next Steps:

  • Please confirm if this issue still occurs in the latest version of Dify.
  • If it is still relevant, comment here to keep the discussion open; otherwise, this issue will be closed automatically in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 27, 2025): Hi, @juniorsereno. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a 404 "Conversation Not Exists" error when sending a second HTTP message in Dify v1.10.0 Cloud. - The error was linked to mismatched user or conversation_id, UI vs API conversation access, or timing of the second message. - I implemented a fix in PR #28462 to resolve this specific issue. - The issue is considered resolved with the merged fix. **Next Steps:** - Please confirm if this issue still occurs in the latest version of Dify. - If it is still relevant, comment here to keep the discussion open; otherwise, this issue will be closed automatically in 15 days. Thank you for your understanding and contribution!
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 cloud 🐞 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#20461
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?