victorsheng opened a new issue, #17885: URL: https://github.com/apache/dolphinscheduler/issues/17885
### 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 a workflow has a schedule with a specific timezone (e.g., `America/Mexico_City`), the dependent task's date range calculation for options like "today", "last1Days", "thisWeek", etc., does not respect the workflow's configured timezone. Instead, it uses the JVM's default timezone. For example: - JVM timezone: `Asia/Shanghai` (UTC+8) - Workflow schedule timezone: `America/Mexico_City` (UTC-6) - Dependent task configured to check "today" The "today" date range is calculated based on `Asia/Shanghai` timezone, not `America/Mexico_City`. This causes incorrect dependency checking in cross-timezone scenarios. ### What you expected to happen The dependent task's date range calculation should respect the workflow schedule's configured timezone. When a workflow is scheduled with `America/Mexico_City` timezone, the "today" date range should be calculated based on Mexico City's local date, not the JVM's timezone. ### How to reproduce 1. Set JVM timezone to `Asia/Shanghai` (or any timezone different from the schedule timezone) 2. Create a workflow with a schedule configured with timezone `America/Mexico_City` 3. Add a dependent task that checks for "today" completion of another workflow 4. Run the workflow when there's a date boundary difference between the two timezones (e.g., when it's Jan 16 in Shanghai but still Jan 15 in Mexico City) 5. Observe that the dependency check uses Shanghai's date range instead of Mexico City's ### 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]
