Page History
...
- 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 and to catch 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 assigned return codes 1 and 2 for signaling success. This allows to later on check the return code and act accordingly by failing or retrying order execution.
At the same time this implies that the job is not considered being failed. As a result
- the JS7 - Task History classifies the job being successfully executed,
- no notifications are created with the JS7 - Monitor view.
These implications might reflect what some users need.
For an alternative solution that fails the offending job and that creates notifications see JS7 - How to retry a job and to catch specific exit codes.
Overview
Content Tools