Sequence Job Trigger

nvalia · Post by **nvalia** » Thu May 14, 2015 7:49 am

Hi All,

I have a Sequence job and I have the Exception Handler --> EMail --> Terminator stage at the end to trap all Exceptions (Failures)

I have checked the 3 options in job properties:
Add Checkpoints so Sequence is Restartable
Log Warnings for activities that finish with status other than OK
Automatically Handle Activities that Fail

In the Seq job, to simplify the design here, we have child Seq Jobs called in Parent/Main Seq

StgSeq --> RefDataSeq --> DimSeq --> FactSeq and all these have Triggers set as Ok Conditional, only then it moves forward.

My expectation was if StgSeq fails (any job within this child Seq fails) it would go to Exception Handler, send email and then Abort gracefully

In this scenario the Main Seq does Abort but I am not getting the email..looking at the log it does not go to the Exception Handler stage and hence no Email..

Is this expected behavior?

Also is this Exception process impacted if in the trigger I use OK Conditional vs Custom -<ActivityVar>.JobStatus = 1, i believe these mean the same ???

Appreciate your reply

Thanks
NV

chulett · Post by **chulett** » Thu May 14, 2015 2:19 pm

First try turning off the "Automatically Handle Activities that Fail" property.

chulett · Post by **chulett** » Thu May 14, 2015 4:40 pm

Then it would seem you have found a bug and you should report it. I'd still be curious what happens if you turn that option off...

ray.wurlod · Post by **ray.wurlod** » Thu May 14, 2015 7:04 pm

The order of precedence is:

a Failure trigger
an Exception Handler
automatic handling
failure

That is, if an activity has a Failure trigger that fires, no call is made to the Exception Handler or any other mechanism. The Failure trigger takes precedence.

Mike · Post by **Mike** » Thu May 14, 2015 7:12 pm

I think Craig is sort of on the right track with this...

I vaguely recall running into something similar a long time back (version 8.7 I think).

At the time it seemed like a timing bug. My issue was resolved when I unchecked the "Log Warnings for activities..." in one of the job sequences. I think it was the parent sequence, but I don't remember for sure.

It seemed like that act of logging a warning probably triggered some product bug.

Mike

nvalia · Post by **nvalia** » Thu May 21, 2015 2:11 pm

Yes this is indeed the problem.

Once I Unchecked the "Log Warnings for Activities.." option and only had the other 2 checked, I started receiving the Failure Notifications as expected.

On reaching out to IBM support, they came back with this same answer..so It is a BUG even in the latest version!

Hopefully they fix it soon, until then this work around does the job!