executions:terminate
Close one stored execution record: sets its status to --terminal_status (`completed`, `failed` or `canceled`; omitted: `canceled`), merges --metadata into the record's metadata, and bumps the node's revision. It records status only: it stops no process or compute (release machines with `compute:release`). Needs the node's owner or an admin. Only a `running` record can be closed: one that is already `completed`, `failed` or `canceled` is refused with 409 naming its status, and stays as it is.
Reference for flywheel executions:terminate.
Command Group
Compute & Executions Commands
Summary
Close one stored execution record: sets its status to --terminal_status (completed, failed or canceled; omitted: canceled), merges --metadata into the record's metadata, and bumps the node's revision. It records status only: it stops no process or compute (release machines with compute:release). Needs the node's owner or an admin. Only a running record can be closed: one that is already completed, failed or canceled is refused with 409 naming its status, and stays as it is.
Effect
DESTRUCTIVE: deletes, overwrites or revokes something
Usage
flywheel executions:terminate <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. | ||
--execution_id | string | Execution record on node_id, from executions:launch or executions:list; not a lease_id. Unknown: 404 where looked up; upload items store it unchecked. | ||
--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 |
|---|---|---|---|---|
--terminal_status | string | canceled | completed, failed, canceled | How the execution ended, stored as the record's status: completed, failed or canceled (omitted: canceled). |
--metadata | json | JSON object merged into the record's metadata: keys you send replace the old values, other keys stay (omitted: \{\}). | ||
--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
Terminate, recording canceled.
flywheel executions:terminate --node_id n_abc --execution_id e1 --expected_revision 6Record that the execution finished, with a result.
flywheel executions:terminate --node_id n_abc --execution_id e1 --expected_revision 6 --terminal_status completed --metadata '{"score":1}'Output
Default format: json.
| Field | Type |
|---|---|
node | object |
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.
approval-sessions:expire
Mark an approval session expired. Grants, leases and campaign budgets are untouched: machines keep running and keep billing until you release them with compute:release. Returns `approval_session` (now expired), `reason` (echoed back, not stored) and two lists, `expired_compute_grant_ids` and `released_lease_ids`, which are always empty (kept so older callers still find the fields).