Introduction

JS7 offers a number of strategies for error handling that are explained from the below matrix.

...

Use Cases

Anchor
use_case_1 use_case_1

Use Case 1: Job error makes 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.

Anchor
use_case_2 use_case_2

Use Case 2: Job error lets order continue

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

...

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

Anchor
use_case_3 use_case_3

Use Case 3: Job error makes order leave the workflow with failed history outcome

In this scenario a job error is caught and is handled in a way that makes the order leave the workflow:

...

For earlier JS7 releases users apply the Finish instruction instead of the Fail instruction in the Catch block to make an order leave the workflow with a failed History outcome.

Anchor
use_case_4 use_case_4

Use Case 4: Job error makes order leave workflow with successful history outcome

Similar to use case 3 in this scenario a job error is caught and is handled in a way that makes the order leave the workflow:

...

For earlier JS7 releases users have to add a dummy job before the Finish instruction that guarantees successful execution in order to specify a successful History outcome.

Anchor
use_case_5 use_case_5

Use Case 5: Job warning lets order continue

In this scenario job errors are considered being warnings based on a selection of job return codes. Such warnings do not require specific error handling, instead the order will continue in the workflow.

...

For earlier JS7 releases Notifications are not sent in case of job warnings.

Resources

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

...