malthe edited a comment on issue #9298: URL: https://github.com/apache/airflow/issues/9298#issuecomment-986574890
I think that's probably the best you can do yes. After each DAG run, use the `on_failure_callback` and `on_success_callback` methods to disable the DAG model (i.e., put it into "off" state). The challenge with task-level "ON HOLD" is for example, how long do you keep the DAG run active before giving up. -- 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
