> For the complete documentation index, see [llms.txt](https://docs.drizz.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drizz.dev/drizz-api-integration/trigger-run.md).

# Trigger Run

The Trigger Run API enables automated execution of one or more Test Plans directly from external systems. It is built for pipelines, nightly regression suites, multi-environment test orchestration, and any workflow that requires programmatic, hands-free execution.

When a Trigger Run request is submitted, Drizz:

1. **Validates the Test Plan configuration**\
   Ensures test cases, device profiles, and execution settings are consistent and executable.
2. **Provisions the required device environment**\
   Allocates emulators, real devices, or web sessions based on the Test Plan settings.
3. **Initiates parallel or sequential execution**\
   Executes test cases based on the order and concurrency rules defined in the Test Plan.
4. **Returns a unique Run ID**\
   This Run ID is used to fetch real-time updates, step logs, execution artifacts, and final results.
5. **Generates aggregated reports automatically**\
   Includes screenshots, recordings, error categorization, retries, and final status summaries.
6. **Supports scale-out execution**\
   Multiple Test Plans can be triggered concurrently across environments, CI agents, or distributed teams.