...

JS7 offers a number of strategies for error handling that are explained with the articles in this sectionfrom the below matrix.

• Error handling includes
  • JS7 - How to detect job errors
  • JS7 - How to handle job errors
    • to decide if a job error can be handled automatically and
      • an order can continue in the workflow,
      • an order should leave the workflow.
    • to decide if a job error requires user intervention,

...

• The History outcome is not determined as the order continues in the workflow. The History outcome will be determined from later workflow instructions.
• Notifications can optionally be sent.
• No User Interventions is appliednot applicable.

Try
    job1
    job2
Catch
Catch-End
job3

...

• The History outcome is specified to be failed as a Fail instruction is used.
• Notifications can optionally be sent.
• No User Interventions is appliednot applicable.

Try
    job1
    job2
Catch
    Fail (leave workflow)
Catch-End
job3

...

• The History outcome is specified to be successful as a Try-Catch instruction is used to handle errors.
• Notifications can optionally be sent.
• No User Interventions is appliednot applicable.

Try
    job1
    job2
Catch
    Finish
Catch-End
job3

...

• The History outcome is not determined: as the order continues in the workflow. The History outcome will be determined from later workflow instructions.
• Notifications can optionally be sent.
• No User Interventions is appliednot applicable.

job1 (return codes: 0=success, 1=warning, >1=error)
job2 (return codes: 0=success, 1=warning, >1=error)
job3 (return codes: 0=success, 1=warning, >1=error)

...

• If any of job1, job2 or job3 completes with return code 1 this is considered a warning. Any other non-zero return codes are considered errors.
• In case of job warnings the order continues with the next instruction in the workflow.
• No User Intervention is appliednot applicable.

Resources

• JS7 - How to detect job errors
• JS7 - How to handle job errors

...