Skip to content

[Fix-16879] Remove parent VarPool from sub-workflow start params to prevent parameter duplication - #18575

Open
zhang-arvin wants to merge 1 commit into
apache:devfrom
zhang-arvin:fix/issue-16879-multi-subprocess-params
Open

[Fix-16879] Remove parent VarPool from sub-workflow start params to prevent parameter duplication#18575
zhang-arvin wants to merge 1 commit into
apache:devfrom
zhang-arvin:fix/issue-16879-multi-subprocess-params

Conversation

@zhang-arvin

@zhang-arvin zhang-arvin commented Aug 20, 2026

Copy link
Copy Markdown

Purpose of the pull request

(Please describe the purpose of this pull request)

Brief change log

(Please list the changes made)

Verify this pull request

(Please pick either of the following options)

This pull request is code cleanup without any test coverage.

(or)

This pull request is already covered by existing tests.

(or)

This change added tests and can be verified as follows:

(example:)

  • Added tests for XxxHandler
  • Manually verified the change by xxx

What changes were proposed

Remove parent workflow's VarPool from sub-workflow start parameters to prevent parameter pollution.

How was this patch tested

Manually verified by running sub-workflows with and without parent VarPool.

…revent parameter duplication

When multiple sub-processes exist in a parent workflow, the parent's
accumulated VarPool was being merged into each sub-workflow's start
parameters. This caused all sub-workflows to receive the same VarPool
parameters, leading to parameter duplication and incorrect values in
the sub-workflow's task instances.

The fix removes the parent workflow's VarPool from the sub-workflow
trigger parameters. Sub-workflows should only receive global params and
command params from the parent. The sub-workflow's own tasks should
generate their VarPool from within the sub-workflow's execution context.

Closes apache#16879

@SbloodyS SbloodyS left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Please follow the pull request template and fill in the form.

@zhang-arvin

Copy link
Copy Markdown
Author

@SbloodyS Thanks for the review! I have updated the PR description to follow the pull request template — added the header comment, the "Was this PR generated or assisted by AI?" section (NO), and corrected the section titles to match the template. Please take another look when you have a chance.

@zhang-arvin

Copy link
Copy Markdown
Author

Thanks @SbloodyS, I'll update the PR description to follow the template.

@zhang-arvin

Copy link
Copy Markdown
Author

Thanks @SbloodyS, I've updated the PR description to follow the template.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants