AZSJTinus opened a new issue, #53444: URL: https://github.com/apache/airflow/issues/53444
### Apache Airflow version 3.0.3 ### If "Other Airflow 2 version" selected, which one? _No response_ ### What happened? The BranchSQLOperator did not skip a downstream BranchSQLOperator. This was working until the 3.0.3 update, eg 3.0.2 seems to have been working fine. The skipping list is empty: <img width="1114" height="61" alt="Image" src="https://github.com/user-attachments/assets/14e7eb98-64d3-43f8-92a8-21a280bfb597" /> ### What you think should happen instead? This issue seems very similar to #52219, a similar change also fixed my issue however, I needed to add the code below to `_ensure_tasks`: ``` from airflow.providers.common.sql.operators.sql import BaseSQLOperator return [n for n in nodes if isinstance(n, (BaseOperator, MappedOperator, BaseSQLOperator))] ``` Afterwards the skipping list contains the BranchSQLOperator: <img width="1135" height="82" alt="Image" src="https://github.com/user-attachments/assets/334402aa-f2e6-4a69-bce4-9229240e035e" /> ### How to reproduce Create a DAG with a BranchSQLOperator that also has a downstream BranchSQLOperator. When running observe that the downstream BranchSQLOperator is not skipped even when it needed to be. ### Operating System Ubuntu 22.04.5 LTS ### Versions of Apache Airflow Providers apache_airflow_providers_common_sql-1.27.3 apache_airflow_providers_microsoft_mssql-4.3.1 apache_airflow_providers_standard-1.4.0 apache_airflow_task_sdk-1.0.3 ### Deployment Virtualenv installation ### Deployment details _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
