TJaniF opened a new issue, #49754: URL: https://github.com/apache/airflow/issues/49754
### Apache Airflow version 3.0.0 ### If "Other Airflow 2 version" selected, which one? breeze ### What happened? I set my Airflow to UTC out of habit, but I live in UTC +1 (winter) / UTC + 2 (summer). No matter which time zone is selected in the Airflow UI, the trigger dag form always assumes my local time zone. Which means if I trigger a dag for the logical date 01.01.2025 00:00 in the UI: <img width="1728" alt="Image" src="https://github.com/user-attachments/assets/ddd759ff-e227-4e12-a315-13c3f019959d"; /> I end up with a run with the logical date 2024-12-31 23:00 - converted to UTC based on me being in UTC +1 in winter time. <img width="1728" alt="Image" src="https://github.com/user-attachments/assets/ed937e16-9e58-49d8-baa7-343b00d84942"; /> The trigger dag form does not say which time zone it is using, I had assumed it used the time zone set in the UI. ### What you think should happen instead? I am not sure what the best solution here is. I think either always using UTC in the trigger form (and display that fact in the UI) or use the time zone the user has set in their Airflow environment (and display that). In the future maybe the option to select the time zone in the trigger form. :) ### How to reproduce Run a dag manually in the UI with a logical date in the past, compare the logical date of the created run with the time you entered. (Only works for people not in UTC 😅 ). You can also select any time zone in the UI and see that it does not effect which time zone the trigger dag form uses. ### Operating System MacOS ### Versions of Apache Airflow Providers not relevant ### Deployment Other ### Deployment details breeze ### Anything else? _No response_ ### 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://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
