DSXchange

I have a sequence that has the "Automatically handle activities that fail" option set and includes an Exception stage to catch them. It has a couple job stages 'A' and 'B' with OK triggers feeding a sequencer (set to "All") and the sequencer feeds another job stage 'C' that ends the sequence.

This morning, job 'B' succeeded but job 'A' failed due to a connection error. Though 'A' failed, it did not fire the Exception stage. Just after logging the failure of 'A', the next entry in the log for the sequence is the "Sequencer ... was entered but never exited".

Is the fact that it was sitting in the sequencer, waiting for job 'A' to finish, the reason it didn't fire off the Exception stage? I would've expected the error from 'A' to fire the exception regardless of any other activity in the sequence.

Try placing a execute command activity with a simple command like to verify whether the exception handler is called or not.[/quote]

Each Sequence stage has a 'Logging Text' property. Use that to leave clues about which stages are actually getting executed.

When an exception stage is triggered, it is reported in the log as: For example: On a typical run, if there is an error, I see this entry and can confirm that the exception was fired. In this instance, no log entry was present to confirm it happened.

I have the "Log warnings after activities that finish with status other than OK" enabled on all my jobs for this purpose. I do use the "Logging text" ability in particular cases.

chulett wrote:Each Sequence stage has a 'Logging Text' property. Use that to leave clues about which stages are actually getting executed.

Does Job A have a specific Failure trigger? This would be used in preference to the Exception Handler in the event of an abort of job A.

No, all jobs in this sequence have only OK triggers. The exception stage is intended to catch everything else. From your responses, I gather that you agree the exception stage should have been triggered?

ray.wurlod wrote:Does Job A have a specific Failure trigger? This would be used in preference to the Exception Handler in the event of an abort of job A.