From b5f8855182e3ce97cf7134761a274e4143250190 Mon Sep 17 00:00:00 2001 From: tekkaya <86028633+tekkaya@users.noreply.github.com> Date: Fri, 12 Jun 2026 12:55:03 -0700 Subject: [PATCH 1/2] Clarify Standalone Activity start Action counting Document that a Start Standalone Activity request which returns an already-running Activity (de-duplicated by Activity ID) is not counted as an Action, unless the start request attaches conflict options to the running Activity. This mirrors the existing de-dup wording for Workflow starts. Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/evaluate/temporal-cloud/actions.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/evaluate/temporal-cloud/actions.mdx b/docs/evaluate/temporal-cloud/actions.mdx index 0c6b3a63c0..5cf9d886be 100644 --- a/docs/evaluate/temporal-cloud/actions.mdx +++ b/docs/evaluate/temporal-cloud/actions.mdx @@ -107,6 +107,9 @@ available endpoints are listed in the following sections: ## Activity {/* #activity */} - **Activity started or retried**. Occurs each time an Activity is started or retried. +- **Standalone Activity started**. Occurs when a [Standalone Activity](/standalone-activity) is started. + - De-duplicated Standalone Activity starts that return an already-running Activity (sharing an Activity ID) do _not_ + count as an Action, unless the start request attaches conflict options to the running Activity. - **Local Activity started**. All [Local Activities](/local-activity) associated with one Workflow Task count as a single Action. Temporal Cloud counts all [RecordMarkers](/references/commands#recordmarker) from each Workflow Task as one action, and not _N_ actions. Note: From f7f1980064c63e59ba9def83fd894cc7395640b7 Mon Sep 17 00:00:00 2001 From: tekkaya <86028633+tekkaya@users.noreply.github.com> Date: Fri, 12 Jun 2026 12:55:03 -0700 Subject: [PATCH 2/2] Reword Standalone Activity Action note in user-facing terms Per review, "conflict options" is not a user-facing concept. Describe the billable case as attaching a callback to the running Activity (e.g. within a Nexus handler using the USE_EXISTING conflict policy). Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/evaluate/temporal-cloud/actions.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/evaluate/temporal-cloud/actions.mdx b/docs/evaluate/temporal-cloud/actions.mdx index 5cf9d886be..902039700b 100644 --- a/docs/evaluate/temporal-cloud/actions.mdx +++ b/docs/evaluate/temporal-cloud/actions.mdx @@ -109,7 +109,8 @@ available endpoints are listed in the following sections: - **Activity started or retried**. Occurs each time an Activity is started or retried. - **Standalone Activity started**. Occurs when a [Standalone Activity](/standalone-activity) is started. - De-duplicated Standalone Activity starts that return an already-running Activity (sharing an Activity ID) do _not_ - count as an Action, unless the start request attaches conflict options to the running Activity. + count as an Action, unless the start request tries to attach a callback to the running Activity — for example, + within a Nexus handler using the `USE_EXISTING` conflict policy. - **Local Activity started**. All [Local Activities](/local-activity) associated with one Workflow Task count as a single Action. Temporal Cloud counts all [RecordMarkers](/references/commands#recordmarker) from each Workflow Task as one action, and not _N_ actions. Note: