Re: [I] I am upgrading from Airflow 2.11.0 to Airflow 3.1.6 and noticed a change in behavior regarding the `ExternalTaskMarker` [airflow]

["jroachgolf84 (via GitHub)" <gi...@apache.org>]

jroachgolf84 commented on issue #61451:
URL: https://github.com/apache/airflow/issues/61451#issuecomment-4244766415

   I'm also working with a team that's seeing this same issue. Here's what they have reported:
   
   > I’ve been using ExternalTaskMarker in Airflow 2 to connect our DAGs and propagate clears downstream without much concern. However, after upgrading to Airflow 3, this no longer seems to work as expected.
   
   When attempting to clear tasks (with “Downstream” selected), the downstream dependencies don’t appear in the UI, and the clears are not being propagated. This suggests it’s not just a UI issue. I’ve attached a screenshot for reference.
   
   Additionally, the Airflow docs mention: “child_task1 will only be cleared if ‘Recursive’ is selected when the user clears parent_task.”
   https://airflow.apache.org/docs/apache-airflow-providers-standard/stable/sensors/external_task_sensor.html
   
   However, I’m not seeing any “Recursive” option in the UI, so I’m unsure whether this is a UI issue or a problem with the operator behavior itself.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org