langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-27 03:01:54 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Variable aggregator does not combine the Knowledge Base result outputs #9579

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

Originally created by @deemeetree on GitHub (Mar 6, 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.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When building a workflow I retrieve two different responses from the same knowledge base (as 2 separate nodes). I then need to combine them in one to send to the LLM node as the context (as described on your Variable Aggregator help page).

✔️ Expected Behavior

I expect that variable aggregator will combine the results of the KB.

❌ Actual Behavior

What happens instead is that it only takes one result.

So the only way for me to fix it now is to replace the Varigable Aggregator node with the Code node and use the following code inside:


function main({arg1, arg2}) {
    return {
        result: [...arg1, ...arg2]
    }
}

Where arg1 and arg2 are the outputs of the two KB searches respectively.

Originally created by @deemeetree on GitHub (Mar 6, 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.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When building a workflow I retrieve two different responses from the same knowledge base (as 2 separate nodes). I then need to combine them in one to send to the LLM node as the context (as described on your Variable Aggregator help page). ### ✔️ Expected Behavior I expect that variable aggregator will combine the results of the KB. ### ❌ Actual Behavior What happens instead is that it only takes one result. So the only way for me to fix it now is to replace the Varigable Aggregator node with the Code node and use the following code inside: ``` function main({arg1, arg2}) { return { result: [...arg1, ...arg2] } } ``` Where `arg1` and `arg2` are the outputs of the two KB searches respectively.
yindo added the 🐞 bug label 2026-02-21 18:36:25 -05:00
yindo closed this issue 2026-02-21 18:36:25 -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#9579
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?