Inconsistent Workflow Execution for AdHoc and Scheduled Orders When Skipping Block Instruction

Current Sittuation
The execution of the workflow differs between AdHoc orders and scheduled orders when the block instruction is skipped.
 
Steps to reproduce:
1. Import the workflow configuration attached.
2. From the workflows tab, Skip the Try instruction from the action menu.
3. Add an Adhoc order to the workflow, only job2 will execute.
4. Add a scheduled order to the workflow, both job1 and job2 are executing. 
(If I skip the block instruction before scheduling the order or after scheduling the order, the outcome remains the same.)
 
Desired Behaviour
Job1 should be skipped for scheduled orders, similar to AdHoc order execution.

Maintainer Notes

• The issue is dismissed as this is the desired behavior. The JS7 architecture is about resilience. This includes that orders are submitted to the Agent that runs the first job in the workflow. This guarantees, that in case of a missing connection between Controller and Agent, the Agent will autonomously start the workflow from the first job.
• If a workflow starts from an Instruction such as a Try/Catch Instruction, If Instruction etc., then the Controller will evaluate the instruction at the point in time of order submission.
• For the use case in question this includes that the order enters the Try/Catch Instruction and remains in front of the next Job Instruction until the order reaches its start time.
• It is understood that some users might wonder why things work like this. At the same time, resilience is a more important goal than user intervention.