temporal activity adds experimental Standalone Activity management

Introduced 2026-04-29 · score 0.96

HOW TO USE IT

When using a dev server, the required Standalone Activity dynamic config is enabled automatically; on a self-hosted server, enable `EnableChasm` and `activity.Enabled` manually. Then use `temporal activity` commands to start or execute an activity, inspect or query it, and wait for its result or cancel or terminate it.

WHY THIS HELPS

Manage Standalone Activities from the CLI in a development or self-hosted server environment.

REQUIREMENTS AND LIMITATIONS

• Version: v1.7.0
• Availability: Experimental
• --activity-id <id> (required): Identifies the Standalone Activity; used to start it and reference it for result, describe, cancel, or terminate.
• --type <activity-type> (required): Activity type to start or execute.
• --task-queue <task-queue> (required): Task Queue for the activity.
• --start-to-close-timeout <duration> (required): Start-to-close timeout; the documented start example uses `5m`, execute uses `30s`.
• --input <json>: Activity input payload; repeatable payload-input option.
• --run-id <id>: Activity Run ID for standalone activity references; if omitted, the latest run is used.
• --query <visibility-query>: Filters activities for `list` or `count`.
• --reason <text>: Cancellation or termination reason; termination defaults to a message with the current user's name.
• EnableChasm (required): Server dynamic config required for Standalone Activity support; dev server enables it automatically.
• activity.Enabled (required): Server dynamic config required for Standalone Activity support; dev server enables it automatically.
• Prerequisite: The release labels Standalone Activity support Experimental.
• Prerequisite: For self-hosted deployments, enable `EnableChasm` and `activity.Enabled`; `temporal server start-dev` enables both automatically.
• For self-hosted server deployments, `EnableChasm` and `activity.Enabled` must be enabled manually.
• The release says these flags will be on by default starting in server v1.32.
• Docs conflict: Current Temporal documentation says Standalone Activities require CLI v1.9.1+ and Server v1.32.0+. That documentation describes newer versions; the v1.7.0 release says the flags will become default in Server v1.32, so its self-hosted setup requirement is retained here.

FIRST-PARTY EVIDENCE

• https://github.com/temporalio/cli/releases/tag/v1.7.0
• https://github.com/temporalio/cli/pull/986
• https://github.com/temporalio/cli/blob/v1.7.0/internal/temporalcli/commands.yaml

Check the installed version and the source before using it. Entry JSON

Report a problem with this card