eladkal commented on issue #28016: URL: https://github.com/apache/airflow/issues/28016#issuecomment-1333633787
>There have been https://github.com/apache/airflow/discussions/22232 on keeping manually triggered DAGs and scheduled DAGs entirely separate - best practice being don't ever manually trigger scheduled DAG runs. I also don't mix scheduled with manual. More over when I need to rerun something I do it with clear - I don't trigger a manual DagRun to compensate. it just make things harder to track. > In our use case, we want to be able to easily trigger a DAG run when there is a gap in execution, and that DAG run should have a data interval that covers any gaps. Like @uranusjr mentioned this is a feature we can do only in Airflow 3 as this is a breaking change (and Airflow is 3 is far far far in the future). I suggest to follow the advice given by @uranusjr to workaround this problem for your case. If no other thoughts I will convert this into a GItHub discussion since this feature request is not actionable -- 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]
