Overview
When using the bulk re-run feature in orchestrations, you may find that filter options and other controls on the page become disabled. This behavior is by design and depends on the orchestration's 'run order' configuration.
How It Works
The availability of filters and re-run options during an execution is determined by whether the orchestration is configured to run tests in a 'Sequential' or 'Parallel' order.
Sequential Run Order
When an orchestration is configured with a Sequential run order, initiating a bulk re-run will cause the user interface to become non-editable. This is intentional to ensure the tests execute in the prescribed order without interruption. While the tests are running, the following options will be disabled:
- All Execution Filter
- Bulk Re-run Option
- Manual Rerun
During this time, a message will appear stating: This option will be available after the test finished executing. This behavior applies to the following orchestration types when configured to run sequentially:
- Single ORC
- Group ORC
- Single TDM ORC
- Group TDM ORC
Once the execution is complete, the controls will become available again.
Parallel Run Order
If the orchestration is configured with a Parallel run order, the filter options and re-run controls will remain enabled and accessible even after initiating a bulk re-run.
Limitations
For orchestrations using a sequential run order, you cannot apply filters or re-run additional tests while a bulk re-run is in progress. You must wait for the current execution to complete before these controls become available again.