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

The IF node stops executing subsequent nodes during the aggregation of results. #13308

New Issue
Closed
opened 2026-02-21 19:11:34 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:11:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @suntao2015005848 on GitHub (Apr 24, 2025).

Originally assigned to: @Nov1c444 on GitHub.

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

1.3.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The IF node stops executing subsequent nodes during the aggregation of results.
if 2 and if 3 , output is true.

✔️ Expected Behavior

❌ Actual Behavior

Image

Image

Image

No response

Originally created by @suntao2015005848 on GitHub (Apr 24, 2025). Originally assigned to: @Nov1c444 on GitHub. ### 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 1.3.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The IF node stops executing subsequent nodes during the aggregation of results. if 2 and if 3 , output is true. ### ✔️ Expected Behavior ### ❌ Actual Behavior ![Image](https://github.com/user-attachments/assets/1b78db61-6cb9-4b14-819b-b7f3ba571e94) ![Image](https://github.com/user-attachments/assets/ead1c8e6-39ea-4c07-9b31-49bc879a640b) ![Image](https://github.com/user-attachments/assets/e14440b8-2b4b-4012-8033-057fba3e6cd1) _No response_
yindo added the 🌊 feat:workflow label 2026-02-21 19:11:34 -05:00
yindo closed this issue 2026-02-21 19:11:34 -05:00
yindo commented 2026-02-21 19:11:35 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 24, 2025):

The issue you're experiencing with the IF node stopping execution during the aggregation of results might be related to how Dify handles parallel branches and the aggregation process. In Dify workflows, the variable aggregation node is used to integrate output results from different branches into a single variable, which is crucial for ensuring a unified configuration for downstream nodes [1].

If the IF node is part of a parallel branch setup, there might be an issue with how nodes execute after parallel branches. In previous versions, there were bugs where nodes after parallel branches executed prematurely or multiple times [2][3]. Although these issues were addressed in later updates, it's possible that similar behavior could affect your setup.

To troubleshoot, ensure that your workflow is structured correctly, especially if using parallel branches. You might want to verify that all branches are properly converging at the variable aggregator and that the aggregator is correctly configured to handle outputs from all branches. If the problem persists, consider checking for any updates or patches that might address this specific issue in version 1.3.0.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Apr 24, 2025): <!-- Answer --> The issue you're experiencing with the IF node stopping execution during the aggregation of results might be related to how Dify handles parallel branches and the aggregation process. In Dify workflows, the variable aggregation node is used to integrate output results from different branches into a single variable, which is crucial for ensuring a unified configuration for downstream nodes <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/node/variable-aggregator.md)</sup>. If the IF node is part of a parallel branch setup, there might be an issue with how nodes execute after parallel branches. In previous versions, there were bugs where nodes after parallel branches executed prematurely or multiple times <sup>[[2]](https://github.com/langgenius/dify/issues/11756)</sup><sup>[[3]](https://github.com/langgenius/dify/issues/13351)</sup>. Although these issues were addressed in later updates, it's possible that similar behavior could affect your setup. To troubleshoot, ensure that your workflow is structured correctly, especially if using parallel branches. You might want to verify that all branches are properly converging at the variable aggregator and that the aggregator is correctly configured to handle outputs from all branches. If the problem persists, consider checking for any updates or patches that might address this specific issue in version 1.3.0. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/d0b53de7-2979-48c6-81cc-4cfd9c2e2f5d?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/d0b53de7-2979-48c6-81cc-4cfd9c2e2f5d?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/d0b53de7-2979-48c6-81cc-4cfd9c2e2f5d?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/d0b53de7-2979-48c6-81cc-4cfd9c2e2f5d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d0b53de7-2979-48c6-81cc-4cfd9c2e2f5d?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/d0b53de7-2979-48c6-81cc-4cfd9c2e2f5d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d0b53de7-2979-48c6-81cc-4cfd9c2e2f5d?feedback_type=other)</sup>
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 🌊 feat:workflow
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#13308
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?