steveahnahn opened a new pull request, #59477: URL: https://github.com/apache/airflow/pull/59477
## Problem Manual triggers of scheduled Dags could generate the same run_id repeatedly (often aligned to the schedule boundary). Triggering the same Dag twice would then fail with a 409 Conflict due to a duplicate run_id ## Solution When a manual trigger provides a logical_date, Airflow still infers the correct data_interval for the run, but it no longer rewrites run_after to the scheduled data_interval.end. This keeps manual trigger run_ids based on the actual trigger time making them unique across repeated manual triggers. - Added a regression test that creates a scheduled Dag, triggers it twice, and asserts the returned dag_run_id values are different: Manual testing in breeze triggering a daily scheduled dag via manual trigger runids: scheduled__2025-12-15T00:00:00+00:00 manual__2025-12-15T04:16:39.584387+00:00 manual__2025-12-15T04:16:50.627593+00:00 manual__2025-12-15T04:18:07.769612+00:00 ## Related Fixes #59342 -- 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]
