temporal activity adds standalone activity lifecycle commands
Introduced 2026-09-14 · score 0.96
HOW TO USE IT
When you need to operate a Standalone Activity, use `temporal activity` to start or execute it, inspect it, wait for its result, or control it by Activity ID. Pause, unpause, reset, and update-options are Experimental; use a list-filter query for supported batch actions.
temporal activity start --activity-id <activity-id> --type <activity-type> --task-queue <task-queue> --start-to-close-timeout 5m --input '{"some-key":"some-value"}'temporal activity describe --activity-id <activity-id>
temporal activity result --activity-id <activity-id>temporal activity cancel --query '<list-filter>' --reason <reason>WHY THIS HELPS
Operate a Standalone Activity from the CLI, including inspecting, waiting for, or controlling it.
REQUIREMENTS AND LIMITATIONS
- Version: v1.9.1
- Availability: `pause`, `unpause`, `reset`, and `update-options` remain Experimental.
- --activity-id (required): Activity ID used to target a specific activity; used by start, describe, result, and single-activity control commands.
- --type (required): Activity type to start.
- --task-queue (required): Task Queue for the activity start example.
- --start-to-close-timeout (required): Start-to-close timeout; the documented start example uses `5m`.
- --input: Activity input payload; the documented example supplies JSON.
- --run-id: Activity Run ID; if omitted for describe or result, the latest run is used.
- --query: List Filter query for matching activities; a query is required instead of `--activity-id` for batch cancel.
- --reason: Reason supplied with cancellation; also used for a batch operation.
- Prerequisite: Standalone Activities require Temporal CLI v1.9.1 or higher and Temporal Server v1.32.0 or higher.
- Prerequisite: Pause, unpause, reset, and update-options are Experimental.
- Works against the local dev server; the described flow can be tried without a Cloud namespace.
- Docs conflict: The release note broadly says operator actions can be batched across a query. Official CLI documentation describes query batching for cancel, terminate, and delete; current Temporal documentation says batch pause, unpause, reset, and update-options are unsupported. Confirm the command’s version-specific support before relying on batching those actions.
FIRST-PARTY EVIDENCE
- https://github.com/temporalio/cli/releases/tag/v1.9.1
- https://github.com/temporalio/cli/blob/v1.9.1/internal/temporalcli/commands.yaml
- https://docs.temporal.io/cli/command-reference/activity
- https://github.com/temporalio/documentation/blob/main/docs/encyclopedia/activities/standalone-activity.mdx
Check the installed version and the source before using it. Entry JSON