ExternalTaskSensor for cross-DAG dependencies in Apache Airflow - Step-by-Step Execution

Process Flow - ExternalTaskSensor for cross-DAG dependencies

Start ExternalTaskSensor

↓

Check if external DAG run exists

↓

Check external task

v +-----> Back to Check↓

Sensor completes

↓

Trigger downstream tasks

↩v +-----> Back to Check

The ExternalTaskSensor waits for a task in another DAG to complete before continuing. It checks repeatedly until the external task finishes, then proceeds.

Execution Sample

Apache Airflow

external_task_sensor = ExternalTaskSensor(
    task_id='wait_for_task',
    external_dag_id='external_dag',
    external_task_id='external_task',
    mode='poke',
    poke_interval=30,
    timeout=600
)

This sensor waits for 'external_task' in 'external_dag' to finish, checking every 30 seconds, timing out after 10 minutes.

Process Table

Step	Check External DAG Run	External Task Status	Action	Sensor State
1	No run found	N/A	Wait and retry after 30s	Waiting
2	Run found	Task running	Wait and retry after 30s	Waiting
3	Run found	Task success	Complete sensor	Success

💡 Sensor completes when external task status is success.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
external_dag_run_found	False	False	True	True
external_task_status	N/A	N/A	running	success
sensor_state	None	Waiting	Waiting	Success

Key Moments - 2 Insights

Why does the sensor keep waiting even if the external DAG run exists?

Because the external task is still running, not yet successful. The sensor waits until the task status is 'success' as shown in execution_table step 2.

What happens if the external DAG run is not found at all?

The sensor waits and retries checking after the poke interval, as shown in execution_table step 1.

Visual Quiz - 3 Questions

Look at the execution table, what is the sensor state at step 2?

A Waiting

B Success

C Failed

D Skipped

💡 Hint

Check the 'Sensor State' column at step 2 in the execution_table.

At which step does the sensor complete successfully?

A Step 1

B Step 2

C Step 3

D Never

💡 Hint

Look for 'Complete sensor' action and 'Success' state in the execution_table.

If the external task never succeeds, what will happen to the sensor state?

A It will become Success anyway

B It will keep Waiting until timeout

C It will fail immediately

D It will skip

💡 Hint

Refer to the sensor behavior in execution_table steps 1 and 2 and the timeout setting in the code sample.

Concept Snapshot

ExternalTaskSensor waits for a task in another DAG to finish.
It checks repeatedly (poke mode) every poke_interval seconds.
If external task is successful, sensor completes.
If no external DAG run or task not done, sensor waits and retries.
Timeout stops sensor after max wait time.

Full Transcript

The ExternalTaskSensor in Airflow is used to wait for a task in a different DAG to complete before continuing. It works by checking if the external DAG run exists and if the external task has succeeded. If the external DAG run is not found or the task is still running, the sensor waits and retries after a set interval. Once the external task is successful, the sensor completes and allows downstream tasks to proceed. This process helps coordinate workflows across multiple DAGs safely and reliably.

Practice

1. What is the main purpose of the ExternalTaskSensor in Airflow?

easy

A. To wait for a task in another DAG to complete before proceeding

B. To trigger a DAG run manually

C. To schedule DAGs at specific intervals

D. To monitor system resource usage

Solution

1. Step 1: Understand the role of ExternalTaskSensor

   The ExternalTaskSensor is designed to pause a task until a specified task in a different DAG finishes successfully.

2. Step 2: Compare with other options

   Triggering DAGs, scheduling, and monitoring resources are handled by other components, not ExternalTaskSensor.

3. Final Answer:

   To wait for a task in another DAG to complete before proceeding -> Option A

4. Quick Check:

   ExternalTaskSensor waits for cross-DAG task completion [OK]

Hint: ExternalTaskSensor waits for tasks in other DAGs [OK]

Common Mistakes:

• Confusing ExternalTaskSensor with DAG trigger
• Thinking it schedules DAGs
• Assuming it monitors system resources

2. Which of the following is the correct way to instantiate an ExternalTaskSensor to wait for task 'task_a' in DAG 'dag_1'?

easy

A. ExternalTaskSensor(task_id='wait_task', dag='dag_1', task='task_a')

B. ExternalTaskSensor(task_id='wait_task', dag_id='dag_1', task_id='task_a')

C. ExternalTaskSensor(task_id='wait_task', external_dag='dag_1', external_task='task_a')

D. ExternalTaskSensor(task_id='wait_task', external_dag_id='dag_1', external_task_id='task_a')

Solution

1. Step 1: Identify correct parameter names

   The ExternalTaskSensor requires external_dag_id and external_task_id to specify the DAG and task it waits for.

2. Step 2: Match parameters with options

   Only ExternalTaskSensor(task_id='wait_task', external_dag_id='dag_1', external_task_id='task_a') uses the correct parameter names and syntax.

3. Final Answer:

   ExternalTaskSensor(task_id='wait_task', external_dag_id='dag_1', external_task_id='task_a') -> Option D

4. Quick Check:

   Use external_dag_id and external_task_id parameters [OK]

Hint: Use external_dag_id and external_task_id parameters [OK]

Common Mistakes:

• Using wrong parameter names like dag_id or external_dag
• Confusing task_id with external_task_id
• Omitting required parameters

3. Given this snippet in DAG 'dag_2':

wait_for_task = ExternalTaskSensor(
    task_id='wait_for_task_a',
    external_dag_id='dag_1',
    external_task_id='task_a',
    mode='reschedule',
    poke_interval=30
)

wait_for_task.execute(context={})

What happens if task_a in dag_1 has not completed yet?

medium

A. The sensor waits and retries every 30 seconds without blocking a worker slot

B. The sensor immediately fails with an error

C. The sensor completes successfully without waiting

D. The sensor blocks a worker slot and retries every 30 seconds

Solution

1. Step 1: Understand mode='reschedule'

   In 'reschedule' mode, the sensor frees the worker slot between pokes, retrying after the poke_interval.

2. Step 2: Analyze behavior when task not complete

   The sensor will keep checking every 30 seconds without blocking a worker slot until the external task finishes.

3. Final Answer:

   The sensor waits and retries every 30 seconds without blocking a worker slot -> Option A

4. Quick Check:

   mode='reschedule' frees worker slot during wait [OK]

Hint: mode='reschedule' frees worker slot during wait [OK]

Common Mistakes:

• Confusing 'reschedule' with 'poke' mode
• Assuming immediate failure if task incomplete
• Thinking sensor completes without waiting

4. You wrote this ExternalTaskSensor:

wait_task = ExternalTaskSensor(
    task_id='wait_task',
    external_dag_id='dag_1',
    external_task_id='task_a',
    timeout=300
)

But the sensor never finishes even after task_a completes. What is the likely cause?

medium

A. The timeout is too high

B. The sensor's execution_date does not match the external task's execution date

C. The task_id is incorrect

D. The sensor is missing poke_interval

Solution

1. Step 1: Understand execution_date matching

   ExternalTaskSensor waits for the external task with the same execution_date by default.

2. Step 2: Identify mismatch issue

   If the sensor's execution_date differs from the external task's, it will wait forever even if the external task completed.

3. Final Answer:

   The sensor's execution_date does not match the external task's execution date -> Option B

4. Quick Check:

   Execution dates must match for ExternalTaskSensor to succeed [OK]

Hint: Check execution_date alignment between DAGs [OK]

Common Mistakes:

• Assuming timeout controls waiting for task completion
• Confusing task_id with external_task_id
• Thinking poke_interval absence causes hang

5. You want to create a cross-DAG dependency where task_b in dag_2 waits for task_a in dag_1 to succeed, but only for the same execution date. Which configuration ensures this behavior and avoids deadlocks?

hard

A. Use ExternalTaskSensor with external_dag_id='dag_1', external_task_id='task_a', and execution_date_fn=lambda x: x - timedelta(days=1)

B. Use ExternalTaskSensor with external_dag_id='dag_1', external_task_id='task_a', and execution_date_fn=lambda x: x

C. Use ExternalTaskSensor with external_dag_id='dag_1', external_task_id='task_a', and default execution_date matching

D. Use ExternalTaskSensor with external_dag_id='dag_1', external_task_id='task_a', and mode='poke' without execution_date control

Solution

1. Step 1: Understand default execution_date behavior

   By default, ExternalTaskSensor waits for the external task with the same execution_date, ensuring correct cross-DAG sync.

2. Step 2: Avoid execution_date shifts

   Using execution_date_fn to shift dates can cause deadlocks or missed dependencies.

3. Step 3: Consider mode

   mode='poke' works but does not affect execution_date matching; default is fine here.

4. Final Answer:

   Use ExternalTaskSensor with external_dag_id='dag_1', external_task_id='task_a', and default execution_date matching -> Option C

5. Quick Check:

   Default execution_date matching avoids deadlocks [OK]

Hint: Default execution_date matching avoids deadlocks [OK]

Common Mistakes:

• Shifting execution_date causing missed dependencies
• Ignoring execution_date alignment
• Misusing mode without fixing execution_date