Triggers a new run of the specified Pipeline.

Creates a Pipeline Run for pipeline_id; the run starts in PENDING status and progresses through the scheduler before executing its Stages against their targeted devices.

About Pipeline Runs

Each time a Pipeline is executed it produces a Pipeline Run, which moves through PENDING → QUEUED → PROCESSING → RUNNING → WAITING → COMPLETE, then SUCCESS or FAILURE — or ends as CANCELLED, TIMEOUT (default 21 days), or INVALID (zero stages). Each Pipeline Run in turn produces one Stage Run per stage, which produces Target Runs for each targeted device.

Common Use Cases

• Kicking off a configured Pipeline (e.g. a multi-step device provisioning or update flow) on demand
• Re-running a Pipeline after fixing its Stages, Target Lists, or Operation Lists

Workflow

1. Configure the Pipeline's Stages, Target Lists, and Operation Lists
2. Create a Pipeline Run to execute the pipeline
3. Track the run's status (and its Stage Runs / Target Runs) through to SUCCESS or FAILURE