executions:launch
Record a new execution on a node (status `running`) and bump the node's revision. It records status only: it starts no process and provisions no compute, and --provider is just a label stored on the record. To run work, acquire a machine with `compute:acquire` (options: `compute:options`), run it there, then close the record with `executions:terminate`. Needs the node's owner or an admin.
Reference for flywheel executions:launch.
Command Group
Compute & Executions Commands
Summary
Record a new execution on a node (status running) and bump the node's revision. It records status only: it starts no process and provisions no compute, and --provider is just a label stored on the record. To run work, acquire a machine with compute:acquire (options: compute:options), run it there, then close the record with executions:terminate. Needs the node's owner or an admin.
Effect
changes data
Usage
flywheel executions:launch <FLAGS>Required flags
| Flag | Value | Default | Choices | Description |
|---|---|---|---|---|
--node_id | string | Node UUID (not a slug) from node_id in hosted:node:list or graph:get. Missing or hidden: 404 where the command loads it. | ||
--expected_revision | integer | revision of node_id (root_node_id for tags) from hosted:node:get or your last write. Stale: 409 (some tools retry once); re-read and retry. |
Optional flags
| Flag | Value | Default | Choices | Description |
|---|---|---|---|---|
--provider | string | Compute provider ID, e.g. lambda (see provider in compute:options). Optional filters: omitted means all. Acquire prefixes an unqualified SKU with it; executions and approval requests just store it. | ||
--metadata | json | JSON object stored on the execution record (omitted: \{\}). Nothing reads it to run work. | ||
--format | FORMAT | json, tsv, csv, table | Output format for command results. | |
--env | PROFILE | Select a CLI profile; unconfigured default requires FLYWHEEL_BASE_URL. | ||
--out | PATH | Write output to a file path, or use - for stdout. | ||
--open | Open browser-bound URLs when supported. | |||
--no-retry | Disable transient-error retries. | |||
--retry-max | N | Maximum transient-error retry attempts. | ||
--wait | Block on async operations until a terminal state is reached. | |||
--wait-timeout | SECONDS | 600 | Seconds to wait for --wait before timing out. Defaults to 600. | |
--allow-self | Allow mutating the currently active credential. | |||
--timeout | SECONDS | Set the per-request timeout budget in seconds. | ||
--idempotency-key | KEY | Reuse an Idempotency-Key so ambiguous write failures can be retried with the same key. | ||
--force | Force safety-gated operations where supported. | |||
--yes | Confirm forced compute:release-all --force. Other runtime commands do not read --yes. | |||
--debug | Print structured request debugging with secrets masked. | |||
--verbose | Print verbose progress for long-running operations. | |||
-h, --help | Show this help. |
Examples
Launch an execution.
flywheel executions:launch --node_id n_abc --expected_revision 5Launch an execution with metadata stored on its record.
flywheel executions:launch --node_id n_abc --expected_revision 5 --metadata '{"purpose":"eval"}'Output
Default format: json.
| Field | Type |
|---|---|
node | object |
execution | object |
compute:status
Read managed compute lease status for the current user and --lease_control_token scope. Returns `compute` with `recommended_next_action` (`acquire_new_lease`, `wait_for_release`, `retry_acquire_active_lease`, `wait_for_active_lease`, `use_active_lease` or `release_or_reacquire`), `active_lease_id` and `leases`. Lease rows include ownership flags so you can distinguish user-owned leases from sponsor-visible campaign leases; only rows with `owned_by_current_user` and `connection_allowed_for_current_user` true can be used for connection or reuse. No SSH private key is returned. When checking a grant-backed lease, reuse the same --compute_grant_id passed to compute:acquire.
executions:list
List the execution records stored on a node (`running`, `completed`, `failed` or `canceled`). They are stored records, not live process state: they change only when `executions:launch` or `executions:terminate` runs.