github-actions[bot] commented on issue #15029: URL: https://github.com/apache/dolphinscheduler/issues/15029#issuecomment-1763678181
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened Subprocess lost Output parameter which is not Direct connected to subProcess If the output parameters are not directly connected to subProcess, subProcess will lose the parameters passed from the upstream. ### What you expected to happen Subprocess can recive Output parameter sucessed. SubProcess type tasks can correctly receive parameters passed from upstream ### How to reproduce 1.SubProcess print parameter transmitted by Upstream node 2.ParentWorkFlow define Output parameter at first node, then print in shell which is second, three node is SubProcess which print parameter which defined in first node. 3 EXCUTE ParentWorkFlow, the Output parameter lost at three nodes Chinese translation: 1 Print the parameters defined in the parent workflow in the subtask output 2 The parent workflow defines output parameters in the first node, prints the output parameters in the second node, and the third node is the subtask (SubProcess also prints the parameters defined in the first node) 3 Execute the parent workflow. The second node can print parameters normally, but the parameters of the third node are lost. <img width="649" alt="image" src="https://github.com/apache/dolphinscheduler/assets/142294782/8ffc847e-55d5-417c-82cb-3a7727bca349"> <img width="1905" alt="image" src="https://github.com/apache/dolphinscheduler/assets/142294782/107055e7-a725-446f-ae29-9ff8591077b7"> ### Anything else _No response_ ### Version dev ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
