Skip to content

add VerisioningOverride to Child Workflow's on start#798

Open
Shivs11 wants to merge 1 commit into
mainfrom
ss/child-workflow-versioning-override-api
Open

add VerisioningOverride to Child Workflow's on start#798
Shivs11 wants to merge 1 commit into
mainfrom
ss/child-workflow-versioning-override-api

Conversation

@Shivs11

@Shivs11 Shivs11 commented Jun 10, 2026

Copy link
Copy Markdown
Member

What changed?

  • WISOTT

Why?

  • Versioning

Breaking changes

  • None

Server PR
temporalio/temporal#10646

START_CHILD_WORKFLOW_EXECUTION_FAILED_CAUSE_UNSPECIFIED = 0;
START_CHILD_WORKFLOW_EXECUTION_FAILED_CAUSE_WORKFLOW_ALREADY_EXISTS = 1;
START_CHILD_WORKFLOW_EXECUTION_FAILED_CAUSE_NAMESPACE_NOT_FOUND = 2;
START_CHILD_WORKFLOW_EXECUTION_FAILED_CAUSE_INVALID_VERSIONING_OVERRIDE = 3;

@Shivs11 Shivs11 Jun 10, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the main reason I chose to have an additional cause here is because there could be a world where the version the user is trying to pin their child workflow on does not exist, and so I thought it's best to have a new cause out here since we should not be starting the child workflow in that case

note: if a user tries to start a non child workflow with a versioning override where the version does not exist, we right now do not start that workflow. The intention was to keep the behaviour consistent.

@Shivs11 Shivs11 marked this pull request as ready for review June 10, 2026 20:19
@Shivs11 Shivs11 requested review from a team June 10, 2026 20:19
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.

2 participants