Apache Airflow 3 Explained: What Changed From Airflow 2 and What to Learn

Airflow 2 reached end of life on 22 April 2026, so Airflow 3 is the version to learn and run in 2027. This guide explains what changed in Airflow 3.0 and the 3.1, 3.2 and 3.3 releases, from the Task SDK and DAG versioning to assets, human-in-the-loop tasks and asset partitioning, with a migration checklist.

GloryTecks Team

Training & Placement Faculty

5 November 2026 6 min read
Share:

Airflow 3 is the version of Apache Airflow to learn and run in 2027. Airflow 2 entered limited maintenance in October 2025 and reached end of life on 22 April 2026, which means it no longer receives fixes of any kind. Airflow 3.0, released in April 2025, was the biggest change in the project's history: a new user interface, DAG versioning, scheduler-managed backfills, a client-server architecture through the Task SDK, and data assets with event-driven scheduling. Releases 3.1 to 3.3 then added human-in-the-loop tasks, asset partitioning, task state and pluggable retry policies. Your Airflow 2 knowledge still helps, but several core ideas now work differently.

Why the move matters now

The Airflow project's supported versions page lists 2.11.2 as the last 2.x release and 22 April 2026 as its end-of-life date. End-of-life versions get no security patches or bug fixes. Some managed providers offer longer support for their own customers, but for open-source deployments the message is clear: plan the migration if you have not already, and learn Airflow 3 if you are starting out.

What changed in Airflow 3.0

The project's Airflow 3 announcement describes the main changes:

ChangeWhat it means in practice
New React-based UIA redesigned interface that moves between task-oriented and asset-oriented views
DAG versioningA run completes using the DAG version it started with, even if a new version is deployed mid-run, and history shows which version ran
Scheduler-managed backfillsBackfills run inside the scheduler, with better control and visibility than the old command-line approach
Task Execution Interface and Task SDKTasks talk to an API server instead of directly to the metadata database, a client-server design with a stronger security model and execution in other environments
Edge ExecutorRuns tasks on edge devices and remote locations, built on the Task Execution Interface
Data assetsDatasets evolved into assets, the basis for data-aware scheduling
External event-driven schedulingDAGs can react to events from messaging systems and to assets updated outside Airflow

The architectural change is the one that matters most for operators. Because tasks no longer reach into the metadata database, workers can run in more isolated environments, and Airflow can eventually run tasks written in other languages.

What 3.1, 3.2 and 3.3 added

  • Airflow 3.1 (September 2025): human-in-the-loop tasks that pause and wait for a person's input in the UI, a React plugin system, deadline alerts (experimental) and a UI available in 17 languages, according to the 3.1.0 announcement.
  • Airflow 3.2 (April 2026): asset partitioning, so only the downstream work for the changed partition runs, plus multi-team deployments (experimental), synchronous deadline alert callbacks and async callables in the PythonOperator, as described in the 3.2.0 announcement.
  • Airflow 3.3 (July 2026): new partition mappers for rolling up and fanning out partitions, a timetable that assigns partition keys at run time, a task and asset state store that survives retries and runs, pluggable retry policies, and an experimental coordinator layer with Java and Go task SDKs, according to the 3.3.0 release notes.

Airflow 2 concepts and their Airflow 3 equivalents

Airflow 2Airflow 3What to do
DatasetsAssetsRename imports and references; use assets for data-aware scheduling
Tasks reading the metadata database directlyTasks use the Task SDK and the API serverReplace direct database access with supported APIs
Backfills from the command lineScheduler-managed backfills, visible in the UIRun and monitor backfills through the new mechanism
A DAG run picking up mid-run code changesDAG versioning, runs finish on the version they started withDeploy freely; review version history after incidents
Ad hoc approval steps built with sensorsHuman-in-the-loop tasks (from 3.1)Use built-in approval tasks where people must decide

Practising Airflow 3 locally

The quickest way to practise is the official Docker Compose setup described in the Airflow documentation, which starts the scheduler, API server, workers and a metadata database on your laptop. Build two or three DAGs that mirror real work: an ingestion DAG that publishes an asset, a transformation DAG scheduled on that asset, and a monthly report DAG you can backfill. Then break things on purpose, such as a failing task, a slow API or a bad deployment, and practise recovering with retries, alerts and the UI. That experience is exactly what interviewers probe.

Migrating from Airflow 2: a checklist

  1. Upgrade to the last 2.x release first. Its deprecation warnings point to most of the changes you need.
  2. Inventory your DAGs, plugins and providers. Note anything that reads the metadata database directly; that pattern no longer works for tasks in Airflow 3.
  3. Replace removed or changed features, such as old dataset code that now uses assets.
  4. Update provider packages to versions that support Airflow 3.
  5. Test in a staging environment with real DAGs, including backfills and failure scenarios.
  6. Migrate in waves, starting with low-risk DAGs, and keep the old environment until critical pipelines have run cleanly for a few cycles.

What to learn in Airflow 3 for 2027

OrderTopicWhy it matters
1DAGs, tasks, operators and the TaskFlow APIThe everyday building blocks
2Scheduling, timetables, retries and alertsReliable unattended pipelines
3Assets and data-aware schedulingPipelines that run when data arrives, not on a guess
4DAG versioning and backfillsSafe changes and historical reprocessing
5Task SDK and deployment architectureHow tasks run, securely and at scale
6Human-in-the-loop, partitioning and deadline alertsThe newer patterns teams are adopting

Keep one principle from Airflow 2: Airflow orchestrates work, it should not do the heavy lifting. Push transformations into Spark, SQL or your warehouse and keep tasks thin. Our comparison of Airflow, Dagster and Prefect covers the alternatives, and the Airflow interview questions show what interviewers ask.

Learning Airflow at GloryTecks

The two-month Apache Airflow course covers orchestration concepts, environment setup with Docker, Airflow's architecture, writing DAGs, scheduling and backfills, passing data, dynamic workflows, sensors and deferrable operators, assets, integrations with databases, cloud services, Spark and dbt, and reliability through retries, alerts and monitoring. The Data Engineering course places Airflow inside a complete pipeline. Both run in classroom batches in Ameerpet and live online.

Is Airflow 2 still supported?

No. Airflow 2 reached end of life on 22 April 2026, with 2.11.2 as the last 2.x release, and end-of-life versions receive no fixes. Some managed providers extend support for their own customers, but open-source users should move to Airflow 3.

What is the biggest change in Airflow 3?

The move to a client-server architecture through the Task Execution Interface and Task SDK, so tasks talk to an API server rather than the metadata database. Alongside it, DAG versioning, scheduler-managed backfills, the new UI and data assets with event-driven scheduling change how pipelines are built and run.

What are assets in Airflow 3?

Assets are the evolution of Airflow 2's datasets: named pieces of data that tasks produce and consume. DAGs can be scheduled to run when an asset is updated, including by systems outside Airflow, and from Airflow 3.2 assets can be partitioned so only affected work runs.

What is the latest version of Airflow?

The Airflow 3.3 line, which started with 3.3.0 in July 2026, is the newest. It added partition mappers, a task and asset state store, pluggable retry policies and experimental Java and Go task SDKs.

How hard is it to migrate from Airflow 2 to Airflow 3?

It depends on how much your DAGs rely on removed features and direct metadata database access. Upgrade to the last 2.x release first to see deprecation warnings, update providers, test real DAGs in staging and migrate in waves, starting with low-risk pipelines.

GloryTecks Team

Training & Placement Faculty

The GloryTecks faculty team mentors learners across Data Science, AI and Data Engineering, with a focus on real-time projects and placement readiness in Hyderabad.

Want to master Data Engineering?

Learn Data Engineering at GloryTecks in Hyderabad, with trainers who have industry experience, real-time projects and placement assistance.

Explore course