Page History

...

• If a child order is suspended then it is put set to the SUSPENDED state. As a result the child order completes its current instruction and stops at the next node. It remains in this state until it is either resumed or cancelled at a later point. If the operation suspending an order is used with the kill force option then the job that is currently executed by the child order will be killed forcibly terminated and the orders will be suspended at the next node.
• 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 force option is used that will kill forcibly terminate a running job executed by the order.
• Note that child orders can take the role of parent orders in nested Fork Instructions.

...