Skip to content

Add optional activity outcome in start activity response#785

Open
ks-temporal wants to merge 10 commits into
mainfrom
ks/ACT-919-activity-outcome
Open

Add optional activity outcome in start activity response#785
ks-temporal wants to merge 10 commits into
mainfrom
ks/ACT-919-activity-outcome

Conversation

@ks-temporal

@ks-temporal ks-temporal commented May 22, 2026

Copy link
Copy Markdown

What changed?
Added a new outcome field of type ActivityExecutionOutcome in
StartActivityExecutionResponse and a new boolean flag of
id_reuse_policy_return_existing_outcome_on_reject in
StartActivityExecutionRequest.

Why?
So that the outcome is included if the execution is already started,
and the activity is already completed, to avoid another query for
the outcome. When a caller's StartActivityExecution short-circuits
to an existing run with the same activity ID because of an ID reuse,
the caller often wants the outcome of the existing run, not just the
identifier or an error pointing at it. Retrieving the outcome in the
response avoids the caller to use a second RPC of
DescribeActivityExecution to retrieve a result that the server
already has cached.

Breaking changes
No

@ks-temporal ks-temporal requested review from a team May 22, 2026 14:26
@CLAassistant

CLAassistant commented May 22, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

Comment thread temporal/api/workflowservice/v1/request_response.proto Outdated
Comment thread temporal/api/workflowservice/v1/request_response.proto Outdated
Comment thread temporal/api/workflowservice/v1/request_response.proto
Comment thread temporal/api/workflowservice/v1/request_response.proto
Comment thread temporal/api/workflowservice/v1/request_response.proto Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants