Tandoy opened a new issue #7417: URL: https://github.com/apache/dolphinscheduler/issues/7417
### 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 There is a workflow that contains two task types: sub-workflow and sql node,the parameter is set to $[yyyyMMdd-1],the sub-workflow parameters are also set $[yyyyMMdd-1].Start scheduling in the evening of 20211214, the number of runs continues to be 20211215.The existing sql node is started in 20211215, and the sub-workflow is started in 20211215 Phenomenon: 1.All sql node dates are T-1 --> 20211214 2.Sub-workflow date is T-1 of the current date --> 20211215 ### What you expected to happen Start the workflow at 20211214, regardless of whether the sql node or the sub-workflow node transfer date is 20211213 ### How to reproduce Create a workflow, which contains sql nodes and sub-workflow nodes. And set the blocking duration to run across days ### Anything else sql node:   sub-workflow node:   ### Version 1.3.6 ### 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]
