Flow Operations v2.2 New

Flow orchestrates rack operations through tasks. Use these guides to choose the execution rule, automate dispatch, or manage a phased firmware rollout.

Guide	Use it to
Operation Rules	Define component ordering, actions, verification, timeouts, and retries.
Task Schedules	Run an operation on a persistent rack scope at an interval, cron time, or once.
Operation Runs	Select firmware targets and manage phased execution with concurrency limits and safety gates.

A rule describes how an operation executes. A schedule describes when to submit tasks. An operation run tracks a selected rollout cohort and its phases. These are separate resources; pausing a schedule or run does not undo hardware actions already performed.

Flow’s interfaces are documented in the generated gRPC reference. The rules guide also covers the Flow CLI. These interfaces are distinct from the REST API reference.

Before operating hardware, review Flow component-manager configuration and the Flow architecture. For firmware-specific prerequisites and target parameters, see Rack and Tray Firmware Updates.

Inventory queries

NVLink Domain topology is nullable when unavailable. Set includeComponents=true to include components; otherwise components is null. When requested but none are known, the Domain’s component list is empty.

Rack, Tray, and NVLink Domain list endpoints use deterministic pagination. When orderBy is omitted, results are ordered by name ascending with an immutable unique identifier as the tie-breaker. See Rack-Level Administration for endpoint links.