Clarify Standalone Activity start Action counting#4704
Draft
tekkaya wants to merge 2 commits into
Draft
Conversation
|
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
tekkaya
force-pushed
the
gokhan/standalone-activity-already-started-not-billed
branch
from
a39e883 to
d7c3ca4
Compare
tekkaya
force-pushed
the
gokhan/standalone-activity-already-started-not-billed
branch
from
d7c3ca4 to
9681f3f
Compare
tekkaya
force-pushed
the
gokhan/standalone-activity-already-started-not-billed
branch
from
9681f3f to
35257ac
Compare
bergundy
approved these changes
Jun 12, 2026
bergundy
reviewed
Jun 12, 2026
| - **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. |
Member
There was a problem hiding this comment.
"Conflict options" isn't a concept that is exposed to users. It'd be better to phrase it as "unless the start request tries to attach a callback to a running execution, for example when used within a Nexus handler with USE_EXISTING conflict policy".
tekkaya
force-pushed
the
gokhan/standalone-activity-already-started-not-billed
branch
from
45aa987 to
ae62196
Compare
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) <noreply@anthropic.com>
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) <noreply@anthropic.com>
tekkaya
force-pushed
the
gokhan/standalone-activity-already-started-not-billed
branch
from
ae62196 to
45727f0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Clarifies in the Temporal Cloud Actions reference (
docs/evaluate/temporal-cloud/actions.mdx, Activity section) that a Start Standalone Activity request which returns an already-running Activity (de-duplicated by Activity ID) does not count as an Action — unless the start request tries to attach a callback to the running Activity, for example within a Nexus handler using theUSE_EXISTINGconflict policy.Notes to reviewers