hussein-awala commented on issue #36178: URL: https://github.com/apache/airflow/issues/36178#issuecomment-1859229094
Here are some concepts in Airflow: - There is a difference between the dag run logical date and starting date; the first one represents the start interval date in the scheduled dag runs and can be any value in the manual run (default is current datetime), and the second is the effective starting date for the dag run. - When you create a manual dag run with a schedule, Airflow will provide the current interval date for this dag run even if it's not ready yet (start_interval_date < starting date <= end_interval date). For the run `manual__2023-12-11T19:51:13.326018+00:00`, the execution/logical date is `2023-12-11T19:51:13.326018+00:00`, and for the run `manual__2023-12-11T19:56:29.214134+00:00` it's `2023-12-11T19:56:29.214134+00:00`. While for the scheduled run `scheduled__2023-12-11T19:55:00+00:00` that process the data interval `(19:55:00, 20:00:00)`, the logical date is `2023-12-11T19:55:00+00:00` which is smaller than the logical date of the second manual dag runs. Since we use the logical date to order the dag runs, Airflow will see the dag runs in this order: - manual__2023-12-11T19:51:13.326018+00:00 - scheduled__2023-12-11T19:55:00+00:00 - manual__2023-12-11T19:56:29.214134+00:00 even if the start date of the second manual dag run is smaller than the start date of the scheduled dag run. The answer to your question: > Is this the expected behaviour? Yes -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
