You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a workflow contains multiple parallel flows and a JOIN transformation is used to wait for their completion, the process will wait indefinitely if an error occurs in just one of the branches. From what I have observed, the JOIN transformation does not recognize the error unless it is explicitly connected to the JOIN transformation itself.
Just wanted to add that this behaviour is also observed when before the "Dummy" action a "simple-evaluation" action blocks a dummy from being executed (correctly). So not only errors, but also explicit non-execution by business logic leads to this "hanging" behaviour.
Activity
hansva commentedon Aug 21, 2026
Could you add a simple reproduction file please
nadment commentedon Aug 21, 2026
Confirmed
[-][Bug]: Bug in the workflow JOIN transformation[/-][+][Bug]: Bug in the workflow JOIN action[/+]leehaut commentedon Aug 25, 2026
.take-issue
gmitter-ef commentedon Oct 7, 2026
Just wanted to add that this behaviour is also observed when before the "Dummy" action a "simple-evaluation" action blocks a dummy from being executed (correctly). So not only errors, but also explicit non-execution by business logic leads to this "hanging" behaviour.