Skip to content

Report child workflow memo/search-attribute encoding errors on the execution future - #2768

Open
Arsen302 wants to merge 1 commit into
temporalio:mainfrom
Arsen302:fix-2761-child-encoding-error
Open

Arsen302 wants to merge 1 commit into
temporalio:mainfrom
Arsen302:fix-2761-child-encoding-error

Conversation

@Arsen302

Copy link
Copy Markdown

What was changed

ExecuteChildWorkflow now resolves the child execution future with the actual memo/search-attribute
encoding error instead of ChildWorkflowExecutionAlreadyStartedError. The result future already got
the right error. Still gated by SDKFlagChildWorkflowErrorExecution, so no replay impact.

Why?

Callers saw "already started" for a child that was never sent to the server.

Checklist

  1. Closes Child workflow memo or search attribute encoding failure is reported as ChildWorkflowExecutionAlreadyStartedError by GetChildWorkflowExecution #2761

  2. How was this tested:
    New unit tests (memo, search attributes, typed/untyped conflict, flag off) fail before and pass after; go test -race ./internal/.

  3. Any docs updates needed?
    No. CHANGELOG entry added under Unreleased/Fixed.

I used AI assistance for analysis and tests; I've reviewed and understand every change.

@Arsen302
Arsen302 requested a review from a team as a code owner October 10, 2026 14:59
@CLAassistant

CLAassistant commented Oct 10, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

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.

Child workflow memo or search attribute encoding failure is reported as ChildWorkflowExecutionAlreadyStartedError by GetChildWorkflowExecution

2 participants