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

Multi node(parallel) after if/else node sometimes fails to process to the next node. #19993

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

Originally created by @AllenHu2024 on GitHub (Oct 29, 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.7.2

Cloud or Self Hosted

Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

Just like the sample below: Two or more nodes(mostly reply node) are added to one branch(parallel run)

Image

✔️ Expected Behavior

Two or more nodes should runs normally after if/else node.

❌ Actual Behavior

Sometimes the graph stops after if/else node, no error found in log. And the result in if/else node has no difference from other normal flows.
After I changed the parallel nodes to sequential, I haven't observed any anomalies so far.

Image Image Image Image
Originally created by @AllenHu2024 on GitHub (Oct 29, 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.7.2 ### Cloud or Self Hosted Self Hosted (Docker), Self Hosted (Source) ### Steps to reproduce Just like the sample below: Two or more nodes(mostly reply node) are added to one branch(parallel run) <img width="639" height="365" alt="Image" src="https://github.com/user-attachments/assets/f1bd22fc-aa7d-4d94-b0d2-abbb3519851e" /> ### ✔️ Expected Behavior Two or more nodes should runs normally after if/else node. ### ❌ Actual Behavior Sometimes the graph stops after if/else node, no error found in log. And the result in if/else node has no difference from other normal flows. After I changed the parallel nodes to sequential, I haven't observed any anomalies so far. <img width="502" height="388" alt="Image" src="https://github.com/user-attachments/assets/b9421e5d-0fa7-4716-9cf4-700a29aa2d9a" /> <img width="525" height="250" alt="Image" src="https://github.com/user-attachments/assets/c021df1e-c14f-4763-8df0-7499deb3259a" /> <img width="594" height="356" alt="Image" src="https://github.com/user-attachments/assets/1b7d430d-b534-4c13-b709-f3c81b1b1b93" /> <img width="1114" height="693" alt="Image" src="https://github.com/user-attachments/assets/658917df-7895-4a70-9576-9203c8abf730" />
yindo added the 🐞 bug label 2026-02-21 20:05:17 -05:00
yindo closed this issue 2026-02-21 20:05:18 -05:00
yindo commented 2026-02-21 20:05:18 -05:00
Author
Owner
Copy Link
Copy Source

@kenwoodjw commented on GitHub (Oct 29, 2025):

Could you provide the minimal steps to reproduce, including the DSL YAML?

@kenwoodjw commented on GitHub (Oct 29, 2025): Could you provide the minimal steps to reproduce, including the DSL YAML?
yindo commented 2026-02-21 20:05:18 -05:00
Author
Owner
Copy Link
Copy Source

@AllenHu2024 commented on GitHub (Oct 29, 2025):

Could you provide the minimal steps to reproduce, including the DSL YAML?

I try to create a new graph and test, it maybe take some time

@AllenHu2024 commented on GitHub (Oct 29, 2025): > Could you provide the minimal steps to reproduce, including the DSL YAML? I try to create a new graph and test, it maybe take some time
yindo commented 2026-02-21 20:05:18 -05:00
Author
Owner
Copy Link
Copy Source

@AllenHu2024 commented on GitHub (Oct 29, 2025):

Image Image [

Test Ifelse (1).txt

](url)

I tried for 9 times and reproduced the issue. Please help find the rootcause. @kenwoodjw

@AllenHu2024 commented on GitHub (Oct 29, 2025): <img width="812" height="635" alt="Image" src="https://github.com/user-attachments/assets/04bc08b6-2e3d-4491-9e41-7ba647d012da" /> <img width="1509" height="715" alt="Image" src="https://github.com/user-attachments/assets/5870a5f6-5c78-4d6b-8c8a-3a43b92f2edb" /> [ [Test Ifelse (1).txt](https://github.com/user-attachments/files/23208533/Test.Ifelse.1.txt) ](url) I tried for 9 times and reproduced the issue. Please help find the rootcause. @kenwoodjw
yindo commented 2026-02-21 20:05:19 -05:00
Author
Owner
Copy Link
Copy Source

@AllenHu2024 commented on GitHub (Oct 29, 2025):

BTW, it happens in high workload(maybe 60% cpu and 60% memory in 2C6G pod)

@AllenHu2024 commented on GitHub (Oct 29, 2025): BTW, it happens in high workload(maybe 60% cpu and 60% memory in 2C6G pod)
yindo commented 2026-02-21 20:05:19 -05:00
Author
Owner
Copy Link
Copy Source

@kenwoodjw commented on GitHub (Oct 29, 2025):

OK, let me troubleshoot

@kenwoodjw commented on GitHub (Oct 29, 2025): OK, let me troubleshoot
yindo commented 2026-02-21 20:05:19 -05:00
Author
Owner
Copy Link
Copy Source

@AllenHu2024 commented on GitHub (Nov 3, 2025):

@kenwoodjw Hi, do you have any updates?
BTW I think the issue occurs not only after if/else node, but also the other parallel nodes

Image

The issue may be related to https://github.com/langgenius/dify/issues/27602

@AllenHu2024 commented on GitHub (Nov 3, 2025): @kenwoodjw Hi, do you have any updates? BTW I think the issue occurs not only after if/else node, but also the other parallel nodes <img width="1433" height="422" alt="Image" src="https://github.com/user-attachments/assets/84cb24cd-07a2-4f03-98c2-ebec35aecab1" /> The issue may be related to https://github.com/langgenius/dify/issues/27602
yindo commented 2026-02-21 20:05:19 -05:00
Author
Owner
Copy Link
Copy Source

@kenwoodjw commented on GitHub (Nov 4, 2025):

Not, can't reproduce in my environment.

@kenwoodjw commented on GitHub (Nov 4, 2025): Not, can't reproduce in my environment.
yindo commented 2026-02-21 20:05:19 -05:00
Author
Owner
Copy Link
Copy Source

@AllenHu2024 commented on GitHub (Nov 4, 2025):

Could you help confirm if there is bug in the PR https://github.com/langgenius/dify/pull/27602

@AllenHu2024 commented on GitHub (Nov 4, 2025): Could you help confirm if there is bug in the PR https://github.com/langgenius/dify/pull/27602
yindo commented 2026-02-21 20:05:19 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 6, 2026):

Hi, @AllenHu2024. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a bug in version 1.7.2 where multiple parallel nodes after an if/else node sometimes fail to proceed without error logs, especially under high workload.
  • You provided screenshots, a test file, and noted the issue might also occur after other parallel nodes.
  • You suspect the problem could be related to PR #27602.
  • A maintainer requested reproduction steps but has been unable to reproduce the issue locally.
  • The issue remains unresolved with no further updates.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 6, 2026): Hi, @AllenHu2024. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a bug in version 1.7.2 where multiple parallel nodes after an if/else node sometimes fail to proceed without error logs, especially under high workload. - You provided screenshots, a test file, and noted the issue might also occur after other parallel nodes. - You suspect the problem could be related to PR #27602. - A maintainer requested reproduction steps but has been unable to reproduce the issue locally. - The issue remains unresolved with no further updates. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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#19993
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?