Pad71 commented on issue #53402: URL: https://github.com/apache/airflow/issues/53402#issuecomment-3077184579
> > However, when the operator is cleared in the UI (e.g., to retry), the associated failed child DAG run remains unchanged. > > This is not something that should be controlled by parameter in operator. You should clear with recursive. > > `Recursive - All the tasks in the child dags and parent dags` https://airflow.apache.org/docs/apache-airflow/3.0.3/core-concepts/dag-run.html#re-run-tasks > > [@bbovenzi](https://github.com/bbovenzi) [@pierrejeambrun](https://github.com/pierrejeambrun) I see that this option is not available in Airflow 3 but it does show up in the docs? I see in [#52130](https://github.com/apache/airflow/pull/52130) it was mentioned as something we used to have as default for Airflow 2 @eladkal I believe that sometimes a user may simply want to reuse an existing child DAG run by clearing it entirely or prevent to clear child dag run at all rather than always triggering a new one. Therefore, instead of a single boolean parameter to control this behavior, it might make more sense to introduce a clear_mode option — allowing users to define how the TriggerDagRunOperator should behave when it's cleared. This could support modes like: "none" (default) – as-is behaviour "failed_tasks" – clear only failed tasks in the triggered DAG This would give users more flexibility when designing DAG chaining or orchestration patterns. -- 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]
