foggiest opened a new issue, #13681: URL: https://github.com/apache/dolphinscheduler/issues/13681
### 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 When i manually execute a Complement-Data instance , the Scheduling time of the generated instance doesn't match the scheduling time that I selected on the parameters-setting page. As the pictures show below: On the parameters-setting page of manually executing ,i selected the scheduling time to be `2023-03-06 00:43:00` But it turns out to be `2023-03-06 08:43:00`. An 8-hour lag occurs. BTW: My DS&server timezone are both Asia/shanghai(UTC+8)   ### What you expected to happen Due to the normal behavior of the Scheduling execution and only the Complement-data instance has the bug, i think there is no error in backend&database side,which means,there exists some timezone-conversion error in the passing between the front-end and the API-server(back-end) I ### How to reproduce 1. Create a test workflow with a single shell type node for the purpose of test 2. Publish the test workflow and manually start a Complement-data instance, select an alternative scheduling time,let's say 2023-03-06 10:00:00, in the setting page 3. Confirm and executes it, check out the scheduling time on the Workflow Instance page ### Anything else _No response_ ### Version 3.1.x ### 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]
