MSerCegeka opened a new issue, #17534: URL: https://github.com/apache/dolphinscheduler/issues/17534
### 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 upgrade from 3.2.2 to 3.3.1, most of our workflows stopped working due to missing variables. This is due to global parameters from sub-workflows not being correctly set for use within their underlying sub-workflows. ### What you expected to happen When setting a global parameter in a sub-workflow, it's values should be propagated to all underlying sub-workflows. ### How to reproduce Create the following situation/workflow: - Workflow A calls Workflow B as a sub-workflow - Workflow B calls Workflow C as a sub-workflow - Workflow B defines a global variable $VALUE - Workflow C contains a shell script to print the $VALUE value - If you start execution from Workflow A, Workflow C does not receive the global $VALUE from Workflow B and prints nothing ### Anything else _No response_ ### Version 3.3.1 ### Are you willing to submit PR? - [ ] 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]
