Run a flow on a Worker

In the flow builder open the run target (Run in cloud) and choose a standalone On-Prem Worker or a Worker cluster, then save. A host that belongs to a cluster is offered only through its cluster. The run executes inside your network and reports every step back, exactly like a cloud run. Connections, AI agent tools, file-transfer routes and telemetry can also be pointed at a Worker. A flow placed on a Worker never moves to the cloud by itself.

A run that cannot start yet has status Waiting and shows why:

Reason	What to do
Waiting for the selected On-Prem Worker to accept this run	The Worker is offline or busy. The run starts once it takes it.
The On-Prem Worker needs free memory on its machine to start this run	Nothing; it starts once memory frees. Add memory or members if it happens often.
The On-Prem Worker needs free disk space on its machine to start this run	Free disk space on the Worker's machine.
The run is queued behind other runs on its On-Prem Worker	Nothing; it starts in turn.
This flow is paused on its On-Prem Worker	Resume the flow, in the app or with the Worker's offline controls.
No On-Prem Worker in the cluster can use all the connections this flow needs	See Members that reach different systems.