Page History

...

• A parent order inherits the successful or unsuccessful outcome of its child orders:
  • As long as any child orders are passing in branches of the ForkList Instruction the parent order will be in a WAITING state.
  • If one or more child orders leave their branches with an unsuccessful outcome then the parent order will be put in the FAILED state.
• The following options apply to error handling with child orders:
  
  • Default: If a job in a child order's branch fails then the child order is assigned the FAILED state. Such child orders require user intervention to resume execution. When resuming a child order, it can be resumed from the same or from any previous or later node in the child order's branch. This includes the option of moving a child order to the branch end.
    • Note that resuming a child order from its branch end will not modify its unsuccessful outcome which . This will be adopted by the parent order that which will then be put in the FAILED state.
    • Users who want to force successful execution of a failed child order should resume the child order from a job node that has been executed successfully or should switch to using the JS7 - Try-Catch Instruction.
  • If a job in a child order's branch fails then the child order terminates immediately and the parent order is put to the FAILED state. This behavior is activated by use of the Join if Failed flag of the Fork Instruction.
• Child orders can be cancelled, however, they will not leave the workflow but will leave their current branch and jump to the Join Instruction. Should child orders not be intended to pass the remaining instructions in a branch, then they can be resumed from the Join Instruction. The cancel operation allows the child order to complete its current node unless the kill option is used that . This will kill a running job executed by the order.
• For details about error handling see JS7 - Fork-Join Instruction.

...