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

Conversation_id does not maintain the conversation context in Chatflow #13223

New Issue
Closed
opened 2026-02-21 19:11:09 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:11:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @dickens88 on GitHub (Apr 22, 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

v1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Hi Team,

It seems the context with Conversation_id doesn't work in Chatflow.

I created a chatflow app which is simply contains a chat node and Agent node. I asked AI check the ip formation about 8.8.8.8 and then try to continue the converation, but it seems it can't see the previous message here.

Image

Is there any limitation about Conversation_id and context here?

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @dickens88 on GitHub (Apr 22, 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 v1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Hi Team, It seems the context with Conversation_id doesn't work in Chatflow. I created a chatflow app which is simply contains a chat node and Agent node. I asked AI check the ip formation about 8.8.8.8 and then try to continue the converation, but it seems it can't see the previous message here. ![Image](https://github.com/user-attachments/assets/1fad7f24-3c57-4a67-94cc-52afe0b83101) Is there any limitation about Conversation_id and context here? ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:11:09 -05:00
yindo closed this issue 2026-02-21 19:11:09 -05:00
yindo commented 2026-02-21 19:11:10 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 22, 2025):

I found a similar issue that was addressed in the Dify repository. The issue was related to the Agent Node in Chatflow lacking conversation history/memory capability. It was resolved by a pull request that added memory features to the Agent Node, allowing it to maintain conversation context [1].

To enable conversation memory in your self-hosted Dify instance, you need to configure the memory functionality by adding the history-messages feature to the Agent plugin’s YAML configuration file strategies/agent.yaml. After modifying the plugin configuration and restarting, you will see the Memory toggle. Click the toggle button on the right to enable memory. Additionally, you can adjust the Window Size using the slider to control how many previous conversation messages the Agent can remember [2][3].

This setup should help maintain the conversation context using the conversation_id.

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 (Apr 22, 2025): <!-- Answer --> I found a similar issue that was addressed in the Dify repository. The issue was related to the Agent Node in Chatflow lacking conversation history/memory capability. It was resolved by a pull request that added memory features to the Agent Node, allowing it to maintain conversation context <sup>[[1]](https://github.com/langgenius/dify/issues/15767)</sup>. To enable conversation memory in your self-hosted Dify instance, you need to configure the memory functionality by adding the `history-messages` feature to the Agent plugin’s YAML configuration file `strategies/agent.yaml`. After modifying the plugin configuration and restarting, you will see the **Memory** toggle. Click the toggle button on the right to enable memory. Additionally, you can adjust the **Window Size** using the slider to control how many previous conversation messages the Agent can remember <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/node/agent.md)</sup><sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/en/plugins/quick-start/develop-plugins/agent-strategy-plugin.md)</sup>. This setup should help maintain the conversation context using the `conversation_id`. <!-- 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/dbd2ebd7-1e6e-4b33-8061-c3c6a370a572?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/dbd2ebd7-1e6e-4b33-8061-c3c6a370a572?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/dbd2ebd7-1e6e-4b33-8061-c3c6a370a572?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/dbd2ebd7-1e6e-4b33-8061-c3c6a370a572?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/dbd2ebd7-1e6e-4b33-8061-c3c6a370a572?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/dbd2ebd7-1e6e-4b33-8061-c3c6a370a572?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/dbd2ebd7-1e6e-4b33-8061-c3c6a370a572?feedback_type=other)</sup>
yindo commented 2026-02-21 19:11:10 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 22, 2025):

Turn on the memory of Agent and LLM node.

@crazywoola commented on GitHub (Apr 22, 2025): Turn on the memory of Agent and LLM node.
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#13223
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?