Introduction

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

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.

...

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

...

• 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

xx

Resources