Details
-
Fix
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
- 2 workflows use the same Resource Lock.
- Screenshot workflows_lock_acquired.png:
- Workflow perform_endofday includes a failed Order. Due to the Options Instruction using the "stopOnFailure": true property ithe failed Order remains with the Job.. The rdb_optimisation Resource Lock continues to be acquired by the Order..
- Workflow roll_over includes an Order waiting for the Resource Lock.
- Screenshot workflows_order_cancelled.png:
- The Order in Workflow perform_endofday has ben cancelled.
- The Order in Workflow roll_over continues to wait for the Resource Lock. The Resource Lock ist not acquired.
Delimitation
- The problem is limited to a situation when
- the Options Instruction using the "stopOnFailure": true property is in place and
- an order fails inside a Resource Lock Instruction.
Desired Behavior
- When a Resource Lock is released then waiting order should acquire the lock and should continue processing.
Workaround
- Users can suspend and resume waiting orders to make them acquire locks.
- Users can restart the Controller to make waiting orders acquire locks.
Patch
- patch for 2.7.1 is available