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

Variable Aggregator doesn't work properly in workflow Released Run mode #17016

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

Originally created by @KnightMord on GitHub (Sep 9, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.8.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image I use 3 continious Parameter Extraction Node to avoid failure, when 1st attempt fails, then goes to 2nd attempt. There's a Variable Aggregator at the end of the 3 Parameter Extraction Nodes, to aggregate the output.

Here's the .yml file of my workflow.
客服推销分析工作流111 (2).yml

✔️ Expected Behavior

The output of the Variable Aggregator should be the first Parameter Extraction Node that successfully generated the output (which means __is_success == 1)

❌ Actual Behavior

In Test Run (while in workflow page), It works fine as expected.

In Releases Run (while in the dedicated page when click "Run"), the Variable Aggregator will always take the output of the 1st Parameter Extraction Node, whether it is success or not. The 2nd/3rd Parameter Extraction Node will still proceed as normal, but the Variable Aggregator always ignore them.

Originally created by @KnightMord on GitHub (Sep 9, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.8.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="2445" height="1060" alt="Image" src="https://github.com/user-attachments/assets/7d426733-2349-4a4b-9f11-280418847c41" /> I use 3 continious Parameter Extraction Node to avoid failure, when 1st attempt fails, then goes to 2nd attempt. There's a Variable Aggregator at the end of the 3 Parameter Extraction Nodes, to aggregate the output. Here's the .yml file of my workflow. [客服推销分析工作流111 (2).yml](https://github.com/user-attachments/files/22238780/111.2.yml) ### ✔️ Expected Behavior The output of the Variable Aggregator should be the first Parameter Extraction Node that successfully generated the output (which means __is_success == 1) ### ❌ Actual Behavior In Test Run (while in workflow page), It works fine as expected. In Releases Run (while in the dedicated page when click "Run"), the Variable Aggregator will always take the output of the 1st Parameter Extraction Node, whether it is success or not. The 2nd/3rd Parameter Extraction Node will still proceed as normal, but the Variable Aggregator always ignore them.
yindo added the 🐞 bug label 2026-02-21 19:30:17 -05:00
yindo closed this issue 2026-02-21 19:30:17 -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#17016
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?