Skip to main content
Workflow runs represent OTA execution in your workspace. Fleet rollouts expose extra controls for workspace owners.

​
Who can control rollouts

The user who created a rollout cannot approve their own run when approval_required is enabled (maker-checker).

​
Approval workflow

When policy has approval_required:
  1. Deploy creates a run in Pending approval.
  2. No OTA trigger is sent to devices yet.
  3. A workspace owner (other than the creator) clicks Approve rollout.
  4. Waves begin according to schedule and strategy.
If approval is not required, the rollout starts immediately after deploy.

​
Pause, resume, and abort

Available on fleet rollouts from the workflow detail panel (Dashboard → Firmware → Workflow runs). Abort is also available from the workflow list (Abort button on fleet runs).

​
Run statuses

​
FAQ

​
Rollout stuck on Paused

Common causes:
  • min_observation_minutes has not elapsed since the last wave.
  • min_success_percent was not met — fix failures, then Resume.
  • Maintenance window ended — rollout resumes when the window opens again.

​
Only some devices updated

Expected with canary or staged_expand. The current stage percent defines how much of the fleet is eligible. Wait for the next stage or check the Rollout stages timeline.

​
Approve button missing

You are not the workspace owner, you are the creator, or the run is not in Pending approval.

​
API

Programmatic control uses the firmware pipeline runs API. See Firmware pipeline API.