Inconsistent handling of suspended cyclic orders

Current Situation

• When a workflow is suspended then orders are displayed with the workflow
  • in the SCHEDULED (yellow) state if orders include a predefined start time.
  • in the BLOCKED (violet) state if orders are added to immediately run in the workflow.
  • in the IN PROGRESS (light-blue) state if orders did pass jobs or other instructions before the workflow was suspended.
• If a cyclic order scheduled to run every minute for two hours is added to a suspended workflow then it is visible from a SCHEDULED (yellow) state and is indicated by a cycle icon.
  • If the cyclic order is suspended (which technically makes no sense as the workflow is already suspended) then instead of a single order the individual 120 orders become visible and carry the suspended state.
  • If the 120 orders related to the cyclic order are resumed then the cyclic order is no longer visible with the workflow. However, the order exists and will start later on when the workflow is resumed.
• See attached screenshots

Desired Behavior

• When suspending a cyclic order then the order should remain a single order and should not display the individual orders included.
• When resuming a suspended cyclic order then the order should become visible with its SCHEDULED (yellow) state with the workflow.