Skipping instructions should be lazy

Current Situation

Orders for a workflow instruction that is being skipped or that is already skipped when an order reaches the instruction are immediately moved to the next instruction regardless of the order's state and schedule.

Consider the use case: a workflow assigns Job 1 to Agent A and Job 2 to Agent B. If job 1 is skipped then the order remains with Agent A and is not moved to Agent B. This implies that at the order's scheduled time Agent A will hand back the order to the Controller that will forward the order to Agent B for the next job. If Agent A is unavailable at the scheduled time then order execution will be delayed.

Examples

• An order with a later start time is added to the workflow and the first instruction is skipped, then the order remains and may only be moved when the start time is reached.
• If an instruction is skipped then a failed order at this instruction remains and may only be moved when it is resumed.

Desired Behavior

Orders at an instruction that is skipped or that is already skipped when an order reaches this instruction should only be moved at the point in time when the order is to process this instruction.

Patch

• patch for 2.7.1 is available
  • Agent: https://download.sos-berlin.com/patches/2.7.1-patch/js7_agent.2.7.1-PATCH.JS-2135_JS-2156_JS-2157.jar [sha256] [sig] [tsr]
  • Controller: https://download.sos-berlin.com/patches/2.7.1-patch/js7_controller.2.7.1-PATCH.JS-2135_JS-2156_JS-2157.jar [sha256] [sig] [tsr]