Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Options Instruction rules error handling for a number of other instructions:

...

  • The motivation for this behavior being that Locks and Notices are considered resources that should not be blocked by failed orders.
    • For example, if a Lock Instruction is used to limit access to a database by parallel jobs. In case of failure of a job the order moves to the begin of the Lock Instruction to free the resource.
    • For example, if a ConsumeNotices Instruction is used to expect and to delete a Notice in transactional manner. In case of failure the order moves to the begin of the ConsumeNotices Instruction to allow other ConsumeNotices Instructions in parallel workflows to delete the Notice and not to delay deletion by a failed order.
  • This behavior similarly applies to use of nested Lock Instructions and nested ConsumeNotices Instructions.
    • A failed order will be moved to the outmost Lock Instruction or ConsumeNotices instruction to free any resources blocked by nested instructions.

...

  • the failed order moves to the outmost Lock Instruction and remains in a failed state.
  • the pdErrorLockBig and pdErrorLockSmall Locks are freed and are availble available to other  byother Lock Instructions.

ConsumeNotices Instruction

...