worldMouse opened a new issue, #14278: URL: https://github.com/apache/dolphinscheduler/issues/14278
### 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 After the execution type of the subworkflow is set to serial wait, it is called and executed by two parent workflows A and B at the same time (the subworkflow are named C1 and C2 respectively according to the call time). C1 can execute normally, but C2 cannot obtain the global variables transmitted by the parent work. 子工作流执行类型被设置为串行等待后，同时被A和B两个父工作流调用执行（根据调用时间先后子工作流分别为命名为C1，C2），C1能正常执行，C2则获取不到父工作流传进来的全局变量。 <img width="935" alt="微信截图_20230605103520" src="https://github.com/apache/dolphinscheduler/assets/129137802/2646f43a-cc13-4139-9be9-52c65ef9d7c5";> C1 <img width="662" alt="微信截图_20230605103539" src="https://github.com/apache/dolphinscheduler/assets/129137802/faf91c5a-0032-4992-97f6-f81bb9ef2c2d";> C2 <img width="653" alt="微信截图_20230605103452" src="https://github.com/apache/dolphinscheduler/assets/129137802/60c3bcc1-7d31-4a16-bcb1-640704080986";> ### What you expected to happen There is a problem with the subworkflow receiving parameters 子工作流接收参数有问题 ### How to reproduce 1. Create subworkflow C, and the execution type is set to serial wait; 2. Create the parent workflow A and B, create the task as the child workflow C at the same time, and set "parameter=abcde" as the global variable; 3. Perform A and B simultaneously. 1.创建子工作流C，执行类型被设置为串行等待； 2.创建父工作流A和B ，A和B 工作流同时创建任务为子工作流C，并全局变量设置 "parameter=abcde"; 3.同时执行A和B。 ### Anything else _No response_ ### Version 3.1.x ### 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]
