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.
Reference for flywheel compute:status.
Command Group
Compute & Executions Commands
Summary
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.
Effect
read-only
Usage
flywheel compute:status <FLAGS>Aliases
cs
Required flags
| Flag | Value | Default | Choices | Description |
|---|---|---|---|---|
--lease_control_token | string | From compute.lease_control_token in compute:acquire; scopes the leases you control (not an SSH credential). No matching lease: empty status, no_active_lease from release-all, 403 on connect or single release. |
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. | ||
--compute_grant_id | string | Grant ID from compute-grants:list or an already_approved compute-grants:request-approval. Acquire requires it; status filters by it. Unknown, inactive, exhausted or bound elsewhere: 403 or 422 approval_required; request approval again. | ||
--limit | integer | Most items to return (omitted: command default). No next page: raise limit or narrow filters. | ||
--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
Check the status of a lease by control token.
flywheel compute:status --lease_control_token tok_42Emit compute status as TSV for scripted monitoring.
flywheel compute:status --lease_control_token=tok_42 --limit=20 --format=tsvOutput
Default format: json.
| Field | Type |
|---|---|
compute | object |
compute:release-all
Queue teardown of every active lease in your --lease_control_token scope and return at once by default; each machine and its storage are then destroyed in the background, nothing snapshotted. --force --yes widens it to all of your active leases. Returns `request_state` `accepted`, `target_count` and `target_lease_ids`, or, when nothing matched, `request_state` `completed`, `outcome` `no_active_lease` and `target_count` 0. Check progress with compute:status. With a token, --wait adds status polling and returns `wait_result`; it does not make the server teardown synchronous.
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.