-
Notifications
You must be signed in to change notification settings - Fork 9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflow terminates after parallel tasks execution, merge node not triggered #12492
Comments
Hey there, @lazyFrogLOL! I'm here to help you with any bugs, questions, or contributions you have for Dify. Let's tackle this issue together! I found a similar unsolved discussion regarding issues with parallel execution in Dify workflows. The discussion mentions a problem with parallel execution in version 0.8.0, where the issue classifier was treated as a parallel execution branch. You can view the discussion here [1]. Regarding your issue, it seems that the merge node is not being triggered after parallel tasks execution. This could be related to how Dify handles the synchronization of results from parallel branches. Dify uses a queue to collect results from each parallel branch and waits for all branches to succeed before proceeding to the merge node [2]. If the merge node is not triggered, it might be due to a failure in synchronizing these results or an issue with the conditions being met simultaneously. You might want to check if all parallel branches are completing successfully and if the conditions for triggering the merge node are correctly defined. Additionally, reviewing the error handling mechanisms for parallel branches might provide insights into why the workflow stops early. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Here is the graph info,
|
Please provide the DSL as well. |
Here is the DSL content.
|
interesting, will take a look, thanks |
Self Checks
Dify version
0.14.2
Cloud or Self Hosted
Self Hosted (Source)
Steps to reproduce
I made a simple workflow test case,
When two IF-ELSE nodes execute in parallel and their results are merged into a subsequent node, if the input satisfies the IF condition of both nodes simultaneously, the subsequent node will not be executed.
I tried to fix this by myself, but the graph engine is too complicated.
✔️ Expected Behavior
The workflow executes properly.
❌ Actual Behavior
The workflow stops early.
The text was updated successfully, but these errors were encountered: