-
Notifications
You must be signed in to change notification settings - Fork 15
Description
I have setup the task dependencies as below
id="1" predecessors="" require_predecessor_success="" instance="tm1serv" process="ProcessOne" pParam="A"
id="2" predecessors="1" require_predecessor_success="" instance="tm1serv" process="ProcessTwo"
id="3" predecessors="" require_predecessor_success="" instance="tm1serv" process="ProcessOne" pParam="B"
id="4" predecessors="3" require_predecessor_success="" instance="tm1serv" process="ProcessFour"
But noticed RushTI is not launching the dependent tasks when threads become available.
Instead it would wait for both tasks 1 and 3 to complete before launching 2 and 4.
I was expecting for an available thread to be utilised by 2 if 1 is complete, or 4 if 3 is complete. Whichever finishes first.
1 and 3 are both running the same process with different parameters, but they have different id so should be independent when referring to them as predecessors. But it seems to treat 1 and 3 as the same and wait for them altogether.