...

JS7 offers a number of strategies for error handling that are explained with the following articles:

...

articles in this section.

• Error handling includes
  • JS7 - How to detect job errors and warnings
  • 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.
• JS7 - How to apply error handling explains the behavior and available JS7 - Workflow Instructions to handle errors.

...

Use Cases

Use Case 1: Job error makes an order stop

In this scenario an order stops subsequently to a job error. The order is put in the failed state. This is the default behavior if no workflow instructions for error handling are used.

• The History outcome is not determined: as the order remains in the workflow. The History outcome will be determined from later User Intervention.
• Notifications can optionally be sent.
• User Interventions include:
  • Resume Order: The order will be continued at the same, at a previous or at a later Workflow Instruction
  • Suspend Order: The order will be suspended and will be resumed or cancelled later on.
  • Cancel Order: The order will be cancelled and the History outcome will indicate the failed order execution.

job1
job2
job3

Explanation:

• If any of job1, job2 or job3 raises an error then the order stops and is put in the failed state.
• User Intervention is required to resume, to suspend or to cancel the order.

Use Case 2: Job error lets an order continue

In this scenario a job error is caught and is handled in a way that lets the order continue.

• 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 applied.

Try
    job1
    job2
Catch
Catch-End
job3

Explanation:

• if any of job1 or job2 in the Try block raises an error then the empty Catch block lets the order continue.
• Leaving the Catch block the order will continue with job3.

Try
    job1
    job2
Catch
    job2a
Catch-End
job3

Explanation:

• if any of job1 or job2 in the Try block raises an error then the order will enter the Catch block.
• In the Catch block job2a is executed.
  • If job2a completes successfully then the order will leave the Catch block and will continue with job3.
  • If job2a fails then the order will be put in the failed state, will be stopped and will remain in the Catch block to wait for User Intervention
  • Consider that Try-Catch instructions can be nested, i.e. in a Catch block another Try-Catch instruction can be used for error handling.

Use Case 3: Job error makes an order finish

x

...

Resources