When we configure an Airflow DAG, we set the default values of various properties, for example, the retry delay. What should we do when we want to overwrite the delay in an Airflow task? What if we’re going to use a different delay in every task?
In this case, we have to include the retry_delay parameter in the constructor of Airflow operators, which delay we want to change. Every Airflow operator supports this parameter because it is defined in the BaseOperator. For the same reason, it is easy to overlook its existence because Airflow documentation does not show the parameters inherited from base classes.
Engineering Reliable AI
Strategies for building production-grade, deterministic AI systems.
"I've learned a lot already from your blog."
— A Substack reader who has pledged $80 per year for this content.
Most AI newsletters hype the latest model releases. This one focuses on the boring, critical engineering required to make those models actually work in production.
Join engineers moving from "notebook" to "production":
-
Architectural Deep Dives: Designing deterministic RAG pipelines and Agentic workflows using schema enforcement (BAML).
-
Production MLOps: Real-world strategies for evaluation, FinOps, and "Shift Left" data quality.
-
System Reliability: Post-mortems on why AI systems fail at scale and how to prevent it.
Subscribe for Free
