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

Each conversation record is a new conversation #8694

New Issue
Closed
opened 2026-02-21 18:27:03 -05:00 by yindo · 7 comments
yindo commented 2026-02-21 18:27:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @if0then1 on GitHub (Feb 27, 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 use docker compose to deployment dify,no source code was modified. auto_generate default value is true,but every conversation record is a new conversation.
So how can I fix the probolem?
Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @if0then1 on GitHub (Feb 27, 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 use docker compose to deployment dify,no source code was modified. auto_generate default value is true,but every conversation record is a new conversation. So how can I fix the probolem? ![Image](https://github.com/user-attachments/assets/9285a3a4-b736-4a5b-947f-093b3454bab2) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 18:27:03 -05:00
yindo closed this issue 2026-02-21 18:27:03 -05:00
yindo commented 2026-02-21 18:27:04 -05:00
Author
Owner
Copy Link
Copy Source

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

@if0then1 Hello! I'm here to assist you with any issues you encounter while using Dify. I can help you solve bugs, answer questions, and even guide you on how to contribute. Let's work together to resolve your concerns while we wait for a human maintainer to join in.

The issue you're experiencing, where each conversation record is treated as a new conversation despite the auto_generate setting being true, might be related to how the conversation_id is being handled in your API requests.

To maintain conversation continuity, ensure that you are using the conversation_id correctly. When starting a new conversation, the conversation_id should be left empty, and a new one will be generated. For subsequent interactions, you must include the generated conversation_id in your API requests to continue the dialogue within the same conversation record. If a previous conversation_id is not used, the system will treat each interaction as a new conversation [1].

If you are already following this process and still encountering issues, it might be worth checking if there are any updates or patches available for your version, as there were known issues in version 0.15.3 related to conversation handling that have been addressed in later updates [2].

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 27, 2025): <!-- Greeting --> @if0then1 Hello! I'm here to assist you with any issues you encounter while using Dify. I can help you solve bugs, answer questions, and even guide you on how to contribute. Let's work together to resolve your concerns while we wait for a human maintainer to join in. <!-- Answer --> The issue you're experiencing, where each conversation record is treated as a new conversation despite the `auto_generate` setting being true, might be related to how the `conversation_id` is being handled in your API requests. To maintain conversation continuity, ensure that you are using the `conversation_id` correctly. When starting a new conversation, the `conversation_id` should be left empty, and a new one will be generated. For subsequent interactions, you must include the generated `conversation_id` in your API requests to continue the dialogue within the same conversation record. If a previous `conversation_id` is not used, the system will treat each interaction as a new conversation <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/application-publishing/developing-with-apis.md)</sup>. If you are already following this process and still encountering issues, it might be worth checking if there are any updates or patches available for your version, as there were known issues in version 0.15.3 related to conversation handling that have been addressed in later updates <sup>[[2]](https://github.com/langgenius/dify/issues/13588)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/71f31f2b-443b-4790-9918-130f9c7e5021?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/71f31f2b-443b-4790-9918-130f9c7e5021?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/71f31f2b-443b-4790-9918-130f9c7e5021?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/71f31f2b-443b-4790-9918-130f9c7e5021?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/71f31f2b-443b-4790-9918-130f9c7e5021?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/71f31f2b-443b-4790-9918-130f9c7e5021?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/71f31f2b-443b-4790-9918-130f9c7e5021?feedback_type=other)</sup>
yindo commented 2026-02-21 18:27:04 -05:00
Author
Owner
Copy Link
Copy Source

@if0then1 commented on GitHub (Feb 27, 2025):

I find the api '/api/chat-messages' paramters like this:
no conversation_id ?
Image

another api '/api/conversations' ,respose result:

{
    "limit": 100,
    "has_more": false,
    "data": [
        {
            "id": "69365d74-4090-4d26-89d7-23b77e77f638",
            "name": "New conversation",
            "inputs": {},
            "status": "normal",
            "introduction": "",
            "created_at": 1740642198,
            "updated_at": 1740642198
        }
    ]
}

@dosu

@if0then1 commented on GitHub (Feb 27, 2025): I find the api '/api/chat-messages' paramters like this: no conversation_id ? ![Image](https://github.com/user-attachments/assets/9cc96a3b-c86a-4ad8-b1bd-1878b6b3af9b) another api '/api/conversations' ,respose result: ``` { "limit": 100, "has_more": false, "data": [ { "id": "69365d74-4090-4d26-89d7-23b77e77f638", "name": "New conversation", "inputs": {}, "status": "normal", "introduction": "", "created_at": 1740642198, "updated_at": 1740642198 } ] } ``` @dosu
yindo commented 2026-02-21 18:27:04 -05:00
Author
Owner
Copy Link
Copy Source

@TigerYangYang commented on GitHub (Feb 27, 2025):

conversation_id

During the first Q&A session, there is no conversion_id, which is produced by the server and will be returned by the server in the event;
During the second Q&A session, the client can continue the Q&A session with the conversion_id.

@TigerYangYang commented on GitHub (Feb 27, 2025): > conversation_id During the first Q&A session, there is no conversion_id, which is produced by the server and will be returned by the server in the event; During the second Q&A session, the client can continue the Q&A session with the conversion_id.
yindo commented 2026-02-21 18:27:04 -05:00
Author
Owner
Copy Link
Copy Source

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

The /api/chat-messages endpoint does require a conversation_id parameter to maintain conversation continuity. When starting a new conversation, you should omit the conversation_id, and the system will generate a new one for you. For subsequent messages in the same conversation, you need to include the generated conversation_id in your requests [1].

Regarding the /api/conversations endpoint, it provides a list of conversation records, including details like id, name, inputs, status, and timestamps. The conversation_id you see in the response (e.g., "id": "69365d74-4090-4d26-89d7-23b77e77f638") is what you should use in your /api/chat-messages requests to continue an existing conversation [2].

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 27, 2025): <!-- Answer --> The `/api/chat-messages` endpoint does require a `conversation_id` parameter to maintain conversation continuity. When starting a new conversation, you should omit the `conversation_id`, and the system will generate a new one for you. For subsequent messages in the same conversation, you need to include the generated `conversation_id` in your requests <sup>[[1]](https://github.com/langgenius/dify/issues/11637)</sup>. Regarding the `/api/conversations` endpoint, it provides a list of conversation records, including details like `id`, `name`, `inputs`, `status`, and timestamps. The `conversation_id` you see in the response (e.g., `"id": "69365d74-4090-4d26-89d7-23b77e77f638"`) is what you should use in your `/api/chat-messages` requests to continue an existing conversation <sup>[[2]](https://github.com/langgenius/dify/blob/main/api/controllers/web/conversation.py)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/752bb956-0b38-4d9c-9a0c-57e289b5ace3?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/752bb956-0b38-4d9c-9a0c-57e289b5ace3?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/752bb956-0b38-4d9c-9a0c-57e289b5ace3?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/752bb956-0b38-4d9c-9a0c-57e289b5ace3?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/752bb956-0b38-4d9c-9a0c-57e289b5ace3?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/752bb956-0b38-4d9c-9a0c-57e289b5ace3?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/752bb956-0b38-4d9c-9a0c-57e289b5ace3?feedback_type=other)</sup>
yindo commented 2026-02-21 18:27:04 -05:00
Author
Owner
Copy Link
Copy Source

@if0then1 commented on GitHub (Feb 27, 2025):

I didn't modify any code and ran the official image 0.15.3 directly. Is there something wrong with the official image? @dosu

对话 ID

第一次问答时，是没有conversion_id的，该id由服务端产生，并在事件中由服务端返回； 第二次问答时，客户端可以使用conversion_id继续问答。

@if0then1 commented on GitHub (Feb 27, 2025): I didn't modify any code and ran the official image 0.15.3 directly. Is there something wrong with the official image? @dosu > > 对话 ID > > 第一次问答时，是没有conversion_id的，该id由服务端产生，并在事件中由服务端返回； 第二次问答时，客户端可以使用conversion_id继续问答。
yindo commented 2026-02-21 18:27:04 -05:00
Author
Owner
Copy Link
Copy Source

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

Yes, there is an issue with the official Dify image version 0.15.3 that affects the handling of conversation_id during API interactions. Specifically, when using the Dify chat-messages API with a conversation_id for multiple rounds of conversation, the input content remains static with the first input and cannot be updated in subsequent rounds. This issue has been resolved in a recent update (PR #7955) [1].

To properly handle conversation IDs, you should omit the conversation_id field in your initial API request to start a new conversation, allowing the system to generate and return a new conversation_id. Use this system-generated conversation_id for continuing the conversation in subsequent API calls [2].

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 27, 2025): <!-- Answer --> Yes, there is an issue with the official Dify image version 0.15.3 that affects the handling of `conversation_id` during API interactions. Specifically, when using the Dify chat-messages API with a `conversation_id` for multiple rounds of conversation, the input content remains static with the first input and cannot be updated in subsequent rounds. This issue has been resolved in a recent update (PR #7955) <sup>[[1]](https://github.com/langgenius/dify/issues/13588)</sup>. To properly handle conversation IDs, you should omit the `conversation_id` field in your initial API request to start a new conversation, allowing the system to generate and return a new `conversation_id`. Use this system-generated `conversation_id` for continuing the conversation in subsequent API calls <sup>[[2]](https://github.com/langgenius/dify/issues/11637)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/19851b44-0fe9-4077-a971-12a74e513092?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/19851b44-0fe9-4077-a971-12a74e513092?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/19851b44-0fe9-4077-a971-12a74e513092?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/19851b44-0fe9-4077-a971-12a74e513092?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/19851b44-0fe9-4077-a971-12a74e513092?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/19851b44-0fe9-4077-a971-12a74e513092?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/19851b44-0fe9-4077-a971-12a74e513092?feedback_type=other)</sup>
yindo commented 2026-02-21 18:27:04 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 27, 2025):

This is a know issue see https://github.com/langgenius/dify/pull/14247 as well.

@crazywoola commented on GitHub (Feb 27, 2025): This is a know issue see https://github.com/langgenius/dify/pull/14247 as well.
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 🤔 cant-reproduce
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#8694
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?