Do you know what I do when I have to test a failing Airflow task? I copy the rendered template and run the code on my own, without Airflow. It is way easier to fiddle with the parameters, for example, to get more verbose output.
To get a rendered template, I used to open an instance of the task, copy the code, and change the parameters to match the execution date I wanted. That is the long and error-prone way to do it.
It turns out that the Airflow command-line interface has a command that generates a rendered template of a given task for the execution date we choose. No more copy-pasting and looking for parameters to change!
All we need is this command:
airflow render dag_id task_id execution_date
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
