Orchestration job with errors in the message file completing successfully

Mike Slee

We have a simple workflow where we use an HTTP input to a communication which returns a document via the Document Request output.

Recently we have had issues with components appearing as missing from the DAS (which they are not) where the job completes successfully and produces a letter with missing components rather than failing.

The issue with the missing components is currently being investigated, but in order for us to trap these situations in the future I would like to know if there is a way of monitoring the exception messages from within the flow and somehow set a failure on the response if possible.

The messages in the message file look like this:

any advice would be welcome, since the OpenText documentation is very 'light' on the subject

Mike Slee

It turns out that there is an Engine Switch that determines what constitutes a job failure, who knew.

The current default setting of the STOPERROR switch is SEVERE which means only severe errors fail the job, minor errors(!) are noted and ignored. Setting the Engine Switch to ERROR solved the issue above regarding the job completing successfully