temporal standalone activity start supports start delay

Introduced 2026-09-11 · score 0.96

HOW TO USE IT

When starting a standalone activity, pass `--start-delay <duration>` to delay its first task; then describe it by activity ID (and optionally run ID) to inspect the result. The v1.9.0 release note says describe text output exposes `StartDelay`.

WHY THIS HELPS

Start a standalone activity with a delay and verify the delay in its description.

REQUIREMENTS AND LIMITATIONS

• Version: v1.9.0
• `--activity-id` (required): Activity ID.
• `--type` (required): Activity Type name.
• `--task-queue` (required): Activity task queue.
• `--start-to-close-timeout`: Maximum time for one activity attempt; either this or `--schedule-to-close-timeout` is required.
• `--start-delay`: Duration before dispatching the first activity task; it does not apply to retry attempts.
• `--run-id`: Activity Run ID; if omitted, describe targets the latest run.
• Prerequisite: Current Temporal documentation says standalone activities require Temporal CLI v1.9.1 or higher and Temporal Server v1.32.0 or higher.
• Support is for standalone activity start/execute options.
• `StartDelay` is exposed in activity describe text output.
• Docs conflict: Current Temporal documentation sets the minimum CLI version for standalone activities to v1.9.1, while this card describes v1.9.0 support. The release page says v1.9.0 was published as a pre-release only; v1.9.1 is the first official v1.9.x release. https://github.com/temporalio/cli/releases

FIRST-PARTY EVIDENCE

• https://github.com/temporalio/cli/releases/tag/v1.9.0
• https://github.com/temporalio/cli/pull/1113
• https://github.com/temporal/documentation/blob/main/docs/cli/command-reference/activity.mdx
• https://github.com/temporal/documentation/blob/main/docs/encyclopedia/activities/standalone-activity.mdx

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

Report a problem with this card