Josh Fell

Nice check to make sure providers would still be compatible with Airflow 2.2! Caught some import issues.

> @josh-fell As I think about adding a flag for retry from failure. I can't wrap my head around the logic for retry in a deferrable operator. Mind share your...

Happy to help out where I can here. Thanks for putting this together @Taragolis!

@thcidale0808 Absolutely! All yours.

@thcidale0808 Are you still working on this one?

@jkarun Thanks for reporting. Does this cause a DAG import error as well or just an issue with the UI view?

Hey @vgupta3! Have you tried applying your `on_failure_callback` to `default_args` instead? Setting [`on_failure_callback` at the DAG level](https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/models/dag/index.html#airflow.models.dag.DAG) applies to the DagRun failing not tasks specifically. > on_failure_callback (DagStateChangeCallback | None)...

Yeah, looking at the Callbacks documentation, I definitely agree it's misleading and could be improved.

> Actually both options are mentioned: https://airflow.apache.org/docs/apache-airflow/stable/logging-monitoring/callbacks.html Callbacks are set at both the DAG and task level in the code snippets, but the copy in the doc only mentions _tasks_....

This has been coming up more frequently for users. I can take on related improvements here.