> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/infra-controller/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/infra-controller/_mcp/server.

# Flow Operations

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](/infra-controller/documentation/operations-day-2/flow-operations/operation-rules) | Define component ordering, actions, verification, timeouts, and retries. |
| [Task Schedules](/infra-controller/documentation/operations-day-2/flow-operations/task-schedules) | Run an operation on a persistent rack scope at an interval, cron time, or once. |
| [Operation Runs](/infra-controller/documentation/operations-day-2/flow-operations/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](https://github.com/dsx-ai-factory/infra-controller/blob/main/rest-api/flow/docs/grpc-api.md). 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](/infra-controller/documentation/configuration-day-1/flow-component-managers) and the [Flow architecture](/infra-controller/documentation/architecture/flow). For firmware-specific prerequisites and target parameters, see [Rack and Tray Firmware Updates](/infra-controller/documentation/operations-day-2/firmware-updates/rack-and-tray-firmware-updates).