Page History

...

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 the following operations:
- Resume Order: The order will be continued at the same, at a previous or at a later Workflow Instructionworkflow 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.

...

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.

...

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

...

if any of job1 or job2 in the Try block raises an error then the order enters the Catch block.
In the Catch block the Fail instruction makes the order leave the workflow. The Fail instruction can be parameterized to either stop an order or to make an order leave the workflow.
An order that entered enters the Catch block will never not execute job3.

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

...

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

...

if any of job1 or job2 in the Try block raises an error then the order enters the Catch block.
In the Catch block the Finish instruction makes the order leave the workflow.
An order that entered enters the Catch block will never not execute job3.

...