Trigger Chain job skips one job

[ekorh]

Hi,

We have a trigger chain job that has 6 different jobs (imports and analytic jobs). Our problem is that the trigger chain always skips the fifth job. But when we run the fifth job manually/individually it works just as expected. 

We also can't really see anything out of the ordinary in logs either? Anyone who might know the reason + fix for this?

Thanks already in advance!

[Manu269]

Can you check wat have been confgured for onFailure :

The behavior of a trigger chain job is configured in the On Failure parameter in the Create New Trigger page, which instructs the job to either continue executing or stop in the event of a failure. If a trigger chain job includes a conflicting job and this job fails, the trigger chain job continues to execute or stop based on the value specified in this parameter.

[ekorh]

Hi,

But the weird thing is, the job runs perfectly normal when we run it individually. 

And during the trigger chain job, the job log does not show anything for this job, not even a failure. If we could detect a failure then this would not be an issue, since we have the ' Continue' on failure configured.

Our problem is, that this job should also be possible to run as a part of the trigger chain, and not just individually.

[ekorh]

Hi,

We have continued our investigation and current findings of the situation are following:

• Trigger chain job has five jobs, lets call them A,B,C,D & E. Trigger chain job has 'Continue on failure' enabled.
• When job C runs, it shows success but every job after C is not being run.
• So the trigger chain job stops at job C, jobs D and E are not run. Even though job C is a successful one, and even though we have the 'Continue on failure' enabled just in case.
• Job C is Azure entitlement import if that makes any difference

[CR]

@ekorh  some time order also required as  per saviynt suggestion

example have CQ  and Acc and account import job in triggerchain

try like  CQ, AccountImport, AccImport

[ekorh]

The problem is that the job was working in this exact order before we changed the trigger chain jobs cron expression. And no other jobs are running while this trigger chain job runs so it is also not a case where two jobs run at the same time and get jammed.

[CR]

Similar type of issue we faced long back, saviynt suggested  like above , it got worked also

[rushikeshvartak]

Can you share job type of each of jobs in trigger chain