Run cycle based job stream submission
You can now use pre-defined run cycles to determine exactly which job stream instances are added to the plan.
This feature allows you to bridge the gap between manual requests and automated
scheduling logic. For more control, you can set a specific time interval to filter which
instances are generated.
|
Scheduling precision: Apply exact run cycle definitions to your submission for more accurate workload generation. |
|
![]() |
Granular control: Use specific time intervals (for example, from 10:00 to 15:00) to filter and submit only the instances you need. |
| Efficiency at a glance: Use a guided wizard and instance accordion to review, expand, or remove specific instances before they are finalized in the plan. |
Explore the benefits of the new wizard for submitting multiple job streams and nested job
streams:
For more information, see Submitting multiple job streams.
