ajsquared opened a new issue, #41014: URL: https://github.com/apache/airflow/issues/41014
### Apache Airflow version Other Airflow 2 version (please specify below) ### If "Other Airflow 2 version" selected, which one? 2.8.3 ### What happened? I have a DAG with a `schedule` of `"20 */3 * * *"` and `catchup=False`. This DAG was paused temporarily, such that we had the `scheduled__2024-07-24T03:20:00+00:00` and `scheduled__2024-07-24T09:20:00+00:00` runs, but the run in between was skipped. We later wanted to manually trigger the missed DAG run. We used `2024-07-24 06:20:00+00` as the logical date in the DAG run trigger form, but this resulted in ``` Data interval start | 2024-07-24, 03:20:00 UTC Data interval end | 2024-07-24, 06:20:00 UTC ``` This is the same interval as the `scheduled__2024-07-24T03:20:00+00:00` run. The `scheduled__2024-07-24T09:20:00+00:00` had ``` Data interval start | 2024-07-24, 09:20:00 UTC Data interval end | 2024-07-24, 12:20:00 UTC ``` This indicates an inconsistency in the treatment of the logical date between manual and scheduled runs. For a scheduled run, the logical date is the data interval start date, but for manual DAG runs it is the data interval end date. We were unable to trigger the DAG run with a logical date of `2024-07-24 09:20:00+00`, which failed with `The logical date 2024-07-24 09:20:00+00:00 already exists`. We ended up doing a manual backfill instead since we couldn't trigger a DAG run with the appropriate data interval. ### What you think should happen instead? Both manual and scheduled runs should treat the logical date the same way. I have no preference on whether it is the data interval start or end date as long as they're consistent. ### How to reproduce 1. Create a DAG with a `schedule` of `"20 */3 * * *"` and `catchup=False` 2. Let one DAG run complete 3. Pause the DAG until after the next DAG run would have started 4. Unpause the DAG run 5. Let the next DAG run complete 6. Attempt to manually trigger the skipped DAG run ### Operating System Debian GNU/Linux 12 (bookworm) ### Versions of Apache Airflow Providers _No response_ ### Deployment Official Apache Airflow Helm Chart ### Deployment details _No response_ ### 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: commits-unsubscr...@airflow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
