DAG expressiveness

[domhues]

Hi everybody, I am trying to get myself familiar with the expressiveness of the workflow language in conductor compared to a generic DAG and I am struggling with defining following type of DAG with conductor's fork join logic:

I.e. Task 3 should only start when Task 1 and 2 finished, but Task 4 should already be able to start if task 2 finishes while task 4 potentially still running.
I stumbled across partial join operators as explained in here but they did not fit the use-case either. Could you point me to a documentation about the expressiveness or hint into the direction which enables these kind of DAGs?

Thanks a lot!

[manan164]

Hi @domhues , I think the below workflow should suffice the use case. Let me know if this works, or we can chat here for more realtime collaboration.

[domhues]

@manan164 Thanks a lot for your answer!
I think your solution does indeed allows Task 4 to execute when Task 2 is done, independent of Task 1 still running.
However, it also adds a new dependency between Task 4 and Task 3, correct? Task 3 is unnecessarily delayed by task 4 while in the DAG above task 3 and 4 can run in parallel.