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

Information Loss Through Variable Aggregator #10856

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

Originally created by @fangao0612 on GitHub (Mar 13, 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

Version 1.0.1

Cloud or Self Hosted

Cloud

Steps to reproduce

when two LLM nodes are connected to a [Template Conversion] node, which is then connected to a [Direct Reply] node, the output successfully combines both results (A+B). However, if the [Template Conversion] node is connected through a [Variable Aggregator] node before connecting to the [Direct Reply] node, the output only shows result B, omitting result A. This appears to be a bug in the system.

When using the variable aggregation pathway, the first result (A) is lost in the process, while only preserving the second result (B). This inconsistent behavior suggests an issue with how the Variable Aggregator handles data from the Template Conversion node.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @fangao0612 on GitHub (Mar 13, 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 Version 1.0.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce when two LLM nodes are connected to a [Template Conversion] node, which is then connected to a [Direct Reply] node, the output successfully combines both results (A+B). However, if the [Template Conversion] node is connected through a [Variable Aggregator] node before connecting to the [Direct Reply] node, the output only shows result B, omitting result A. This appears to be a bug in the system. When using the variable aggregation pathway, the first result (A) is lost in the process, while only preserving the second result (B). This inconsistent behavior suggests an issue with how the Variable Aggregator handles data from the Template Conversion node. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:51:58 -05:00
yindo closed this issue 2026-02-21 18:51:58 -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#10856
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?