...

• A number of jobs are executed in sequence.
• If one or more jobs fail with exit code 1 then the jobs should be repeated for a number of times. For any other non-zero exit codes the order should be put to a failed state and should wait for user intervention, for example to resume or to cancel the failed order.
• A similar related scenario is available from JS7 - How to retry a job in case of specific exit codes.

...

• The right Fail Instruction fails the order with a return code value 2.
• In addition, a message can be added that becomes visible with the JOC Cockpit GUI for the failed order.
• The uncatchable checkbox is used to indicate that the failed order cannot be picked by the outer Retry Instruction. Instead, the order will remain with its current position in a failed state and waits for user intervention.

Implications

In this scenario the job is configured to consider any non-zero return code signaling failure. This requires use of a Try / Catch Instruction to handle errors.

This implies that

• the JS7 - Task History classifies the job being failed,
• a notification is created for each failed execution that is visible from the JS7 - Monitor view and that can be forwarded by use of a JS7 - Notification.

These implications might reflect what some users need.

For an alternative solution that does not fail the offending job and that does not create notifications see JS7 - How to retry a job in case of specific exit codes.