Why does the ExternalTaskSensor get stuck?
Airflow

Why does the ExternalTaskSensor get stuck?

How to fix the stuck ExternalTaskSensor
Bartosz Mikulski
Bartosz Mikulski – 1 min read

If you configured an ExternalTaskSensor in Airflow to wait until a task in another DAG finishes (or the entire DAG finishes), you have probably noticed that it behaves surprisingly. Most data engineers assume that it is a bug, and their sensor gets stuck for whatever reason. I have to admit that I find it annoying because the documentation of the ExternalTaskSensor does not warn us about it.

ExternalTaskSensor works only if the other DAG has the same execution date equal to the expected execution date. Sure, you can specify the execution time delta, but it is not a time range.

For example:

  • The execution date of the DAG that contains the sensor is: 2020-10-01 14:00:00
  • The execution delta = 3 hours

In this situation, the other DAG’s execution date must be 2020-10-01 11:00:00.

I think that most data engineers expect that delta = 3 hours means that the other DAG may execute at any time between 11:00 and 14:00.

Older post

How to render an Airflow template for testing

How to generate the code of an Airflow task from a template and a given execution date

Newer post

How to trigger an Airflow DAG from another DAG

How to trigger another DAG from an Airflow DAG

Related Posts

Airflow Prophet

Anomaly detection in Airflow DAG using Prophet library

How to detect problems in Airflow pipeline using Prophet for time series anomaly detection
Published on: 12 Feb 2021

Airflow

How to restart a stuck Airflow DAG

What to do when an Airflow DAG gets stuck and does not want to run
Published on: 31 Dec 2020

Airflow

Why does the DayOfWeekSensor exist in Airflow?

How to make an Airflow DAG wait until a specified day of the week
Published on: 30 Dec 2020