Execution
- A Cycle Instruction spawning a complete workflow is an equivalent to a cyclic order from a Schedule.
- In addition, a Cycle Instruction can be used to execute parts of a workflow in cycles.
Efficiency

Schedules create a number of order instances for each period in a cycle, Running a single workflow every 30s counts to 2880 orders per day.
Cycle Instructions cause cyclic execution of a workflow from a single order.
Processing of cyclic workflows is by far more efficient than the use of cyclic orders.

Error Handling
- Failure
  - If a job in a workflow fails then this will occur for each individual order instance of a cyclic order.
  - If a job within a Cycle Instruction fails then, depending on the error handling in place, any cycles that would occur while an order is in a failed state will be skipped.
- Notification
  - For each failed order instance of a cyclic order a JS7 - Notification is created.
  - For the single order of a cyclic workflow a single Notification is created.
- Intervention
  - Any operations on cyclic orders are applied to all order instances including, for example, resuming execution after failure. This results in parallel execution of orders previously scheduled for execution in intervals.
  - For cyclic workflows there is a single order that waits for user intervention.
Logging
- For each order instance of a cyclic order a separate entry is created in the JS7 - Order History and in the JS7 - Task History.
- For a cyclic workflow there is a single entry in the Order History. The log output of each cycle is appended to this entry. Individual entries per job execution are added to the Task History.

Space shortcuts

Page tree