GitHub user Naikless edited a discussion: Manual DAG execution with defined delay
In my use case, Airflow is mostly used to orchestrate and define chains of tasks in reproducible DAGs. Most of the time, the resulting DAGs are triggered manually via the Web interface. It would be very convenient to be able to trigger DAGs manually with a certain delay or to actually start only at a specified time. Until today, I was under the impression that airflow doesn't provide this out of the box (see e.g. https://github.com/apache/airflow/discussions/33068#discussioncomment-6629831) However, I discovered that that the current version provides a handy workaround for this: If you manually trigger a DAG via the UI and set the logical date to the future, DAG tasks won't start until the specified time has come. This seems to stem from this change https://github.com/apache/airflow/pull/46663. However, there is some debate if this behavior is to be desired https://github.com/apache/airflow/pull/65856. So my question would be: To what extend can I expect this behavior to work in the future? Are there drawbacks? Most of the technical details mentioned in the linked discussions are frankly lost on me, but it feels like this is a rather "hacky" circumstance, although the resulting behavior (being able to set a start time for your manually triggered DAG tasks in the UI) is arguably exactly what I would have wished for. GitHub link: https://github.com/apache/airflow/discussions/68383 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
