Force Start Box and Child jobs at the sametime causing incorrect execution order

[VEERA V]

Consider there are of two jobs [job A(FW job) and job B ] inside a BOX. Both Box and its sub jobs are all terminated State.

If we force Start 3 jobs ( BOX job and its A and B jobs) at the same time by selecting all three from WCC console, for some time, job B is getting triggered first before Job A to start eventhough B is dependent on job A. Please advise why this is happening.

Please What's the right approach to be followed here? We should only trigger terminated BOX job alone ? ( assuming all sub jobs are failed/not running state)

Thanks in advance.

[Michael Woods]

Hi Veera,

Yes, you should only force start the box and then the jobs in the box will follow their normal flow.  If you force start all three, you are asking the scheduler to do just that, start all three without any considerations to the conditions that normally apply.

Regards,

Mike

[Venkateswarlu Dondapati]

Issuing force start to a box alone is sufficient. 

Force start should be used under specific abnormal scenarios only.
However if there is a possibility of workflow in which some jobs in a box are still not completed before issuing force start to a box, then issue CHANGE_STATUS/INACTIVE to the box as a best practice, before issuing force start to a box.