Cloud Orchestrator Trigger created jobs in wrong order

Help Orchestrator
, ,
1

Hi everyone,

I have two Triggers set up in Cloud Orchestraor. Trigger ‘A’ that fires at 15:00:00, and Trigger ‘B’ that fires at 15:00:01 (one second after Trigger ‘A’).

Strangely I had Trigger ‘B’ create a job and begin execution before Trigger ‘A’, and the job created by Trigger ‘A’ was queued behind the job created by Trigger ‘B’.

Has anyone else experienced this? If so any ideas on what could have caused this?

Thanks,

2

Hi @DanielY

Welcome to Community

Can you check the User, Machine and process in the Trigger

image
image727×320 9.4 KB

Regards
Gokul

3

Hi @DanielY

Is the Trigger B has set to high priority?

Regards

4

Both ‘A’ and ‘B’ Triggers are set to any User and any Machine. And they each run different processes.

Thanks,

5

Hi @pravin_calvin

No, Trigger ‘B’ does not have high job priority. Both Trigger ‘A’ and ‘B’ are set to Normal priority.

Thanks,

6

HI @DanielY

Can you share the screenshot of the trigger.

Trigger A - 0 0 8 ? * MON-FRI *

Trigger B - 0 03 8 ? * MON-FRI *

Can you change the Job priority → Inherited

Regards
Gokul

7

I have two Triggers set up in Cloud Orchestraor. Trigger ‘A’ that fires at 15:00:00, and Trigger ‘B’ that fires at 15:00:01 (one second after Trigger ‘A’).

Are you sure it was one second of delay between the two? Time triggers in Orcherstrator only allow one minute of resolution.

Anyway, you should not use trigger time to order job execution with very small time difference (<5 minutes). Instead, you should use other synchronization mechanisms, like queues with the producer-consumer pattern.

1 Like