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

End node should optionally stop any parallel flow #8055

New Issue
Closed
opened 2026-02-21 18:23:41 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 18:23:41 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Feb 7, 2025).

Self Checks

  • 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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I have a workflow that runs in parallel a deeper validation on the input variables
The parallel branches merge into the workflow main job to produce an output.

If any of the parallel validations fail I want the workflow to stop executing and return a response with an error output

The "End" node does not end the workflow, it outputs its value and anything other parallel branch keeps running
To stop the entire workflow I have to raise an exception with console.error("message") or Throw or the equivalent in python.
I would like an option in the "End" node to make it stop the workflow allowing me to output complex objects other than a string message.

The same node would become useful in the "Iteration" node to stop the iteration earlier.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @DavideDelbianco on GitHub (Feb 7, 2025). ### Self Checks - [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. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. I have a workflow that runs in parallel a deeper validation on the input variables The parallel branches merge into the workflow main job to produce an output. If any of the parallel validations fail I want the workflow to stop executing and return a response with an error output The "End" node does not end the workflow, it outputs its value and anything other parallel branch keeps running To stop the entire workflow I have to raise an exception with console.error("message") or Throw or the equivalent in python. I would like an option in the "End" node to make it stop the workflow allowing me to output complex objects other than a string message. The same node would become useful in the "Iteration" node to stop the iteration earlier. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 18:23:41 -05:00
yindo closed this issue 2026-02-21 18:23:41 -05:00
yindo commented 2026-02-21 18:23:41 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Feb 7, 2025):

Could be related to #12217

@DavideDelbianco commented on GitHub (Feb 7, 2025): Could be related to #12217
yindo commented 2026-02-21 18:23:41 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 10, 2025):

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

Issue Summary:

  • Enhancement requested for the "End" node to stop the entire workflow if any parallel validation fails.
  • Similar feature suggested for the "Iteration" node for early halting of iterations.
  • Potential relation to issue #12217.
  • Currently unresolved.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Mar 10, 2025): Hi, @DavideDelbianco. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - Enhancement requested for the "End" node to stop the entire workflow if any parallel validation fails. - Similar feature suggested for the "Iteration" node for early halting of iterations. - Potential relation to issue #12217. - Currently unresolved. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 18:23:41 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Mar 10, 2025):

This kind of node does not exist yet, and I would love to be a le to stop the workflow with a "stop node" that allows me to return a response

@DavideDelbianco commented on GitHub (Mar 10, 2025): This kind of node does not exist yet, and I would love to be a le to stop the workflow with a "stop node" that allows me to return a response
yindo commented 2026-02-21 18:23:41 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 10, 2025):

@takatost, the user @DavideDelbianco has indicated that the enhancement for a "stop node" to halt workflows is still relevant and needed. Could you please assist them with this issue?

@dosubot[bot] commented on GitHub (Mar 10, 2025): @takatost, the user @DavideDelbianco has indicated that the enhancement for a "stop node" to halt workflows is still relevant and needed. Could you please assist them with this issue?
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 💪 enhancement
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#8055
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?