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

The issue of enabling memory windows in LLM nodes #3507

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

Originally created by @LouisCan on GitHub (May 21, 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.5

Cloud or Self Hosted

Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

When enabling memory functions in configuring Language Model (LLM) nodes, if multiple LLM nodes are used in a process orchestration: once the memory window is activated, the system will automatically include the "role": "assistant" part of the output from each LLM node in the process into the historical memory library. This leads to information redundancy and confusion because each LLM node's system directives are different, causing the current LLM's return results to be disordered.

✔️ Expected Behavior

Only the history of the current node is enabled

❌ Actual Behavior

Returns all history

Originally created by @LouisCan on GitHub (May 21, 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.5 ### Cloud or Self Hosted Self Hosted (Docker), Self Hosted (Source) ### Steps to reproduce When enabling memory functions in configuring Language Model (LLM) nodes, if multiple LLM nodes are used in a process orchestration: once the memory window is activated, the system will automatically include the "role": "assistant" part of the output from each LLM node in the process into the historical memory library. This leads to information redundancy and confusion because each LLM node's system directives are different, causing the current LLM's return results to be disordered. ### ✔️ Expected Behavior Only the history of the current node is enabled ### ❌ Actual Behavior Returns all history
yindo closed this issue 2026-02-21 17:58:38 -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
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#3507
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?