styndall opened a new issue, #77141: URL: https://github.com/apache/airflow/issues/77141
In the Grid view, the Dag run tooltip shows **date, Run ID, state and duration**. The date is the run's `run_after`, the trigger time, shown in the browser's local time zone. For scheduled runs that's close to the data processed. For **manual and backfill runs, nothing in the tooltip shows the logical date or data interval**, which decide what the tasks process. ### Example (Airflow 3.3.2, browser at UTC−5) A manual run with `logical_date=2026-11-13T12:00Z` and data interval 2026-11-13 00:05 → 2026-11-14 00:05Z, triggered at 2026-11-16 00:27Z. The tooltip shows `2026-11-15 19:27:01` and `manual__2026-11-16T00:27:01…`. Nothing indicates the run is for 2026-11-13. This made a backfill-by-hand error easy to miss. In the Trigger dialog we picked 2026-11-13, and the time defaulted to the current local time (19:10). That stored `logical_date=2026-11-14T00:10Z`, a different UTC day. For daily DAGs that use the logical date's calendar day, that's the wrong partition, and neither the dialog nor the tooltip shows it. ### Proposal 1. Grid run tooltip: add the logical date and data interval, at least for manual and backfill runs. The strings `common:logicalDate`, `common:dataIntervalStart` and `common:dataIntervalEnd` already exist. 2. Trigger dialog: show the resulting logical date in UTC (or the DAG's time zone) next to the local-time input. Related: #74482. -- 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]
