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

chatflow-memory-error #3587

New Issue
Closed
opened 2026-02-21 17:59:36 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:59:36 -05:00
Owner
Copy Link
Copy Source

Originally created by @wangtianqi1993 on GitHub (May 22, 2024).

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).
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.6

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

The chatflow that includes tools has enabled memory, and currently, the final output of the entire process is stored as the assistant's answer result in the conversation history. For example, if a LLM is followed by a tool, the output of the tool will be used as the answer for the current round of conversation. Such historical memory can mislead the LLM

✔️ Expected Behavior

The output of the LLM should be taken directly as the answer, rather than the final output of the entire chatflow being used as the answer.

❌ Actual Behavior

The chatflow that includes tools has enabled memory, and currently, the final output of the entire process is stored as the assistant's answer result in the conversation history. For example, if a LLM is followed by a tool, the output of the tool will be used as the answer for the current round of conversation. Such historical memory can mislead the LLM

Originally created by @wangtianqi1993 on GitHub (May 22, 2024). ### 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] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.6 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce The chatflow that includes tools has enabled memory, and currently, the final output of the entire process is stored as the assistant's answer result in the conversation history. For example, if a LLM is followed by a tool, the output of the tool will be used as the answer for the current round of conversation. Such historical memory can mislead the LLM ### ✔️ Expected Behavior The output of the LLM should be taken directly as the answer, rather than the final output of the entire chatflow being used as the answer. ### ❌ Actual Behavior The chatflow that includes tools has enabled memory, and currently, the final output of the entire process is stored as the assistant's answer result in the conversation history. For example, if a LLM is followed by a tool, the output of the tool will be used as the answer for the current round of conversation. Such historical memory can mislead the LLM
yindo added the 🐞 bug label 2026-02-21 17:59:36 -05:00
yindo closed this issue 2026-02-21 17:59:36 -05:00
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#3587
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?