Skip to content

Deferred AzureDataFactoryRunPipelineOperator + Airflow 3.0.3 failure #55728

Closed

Description

@BasPH

Apache Airflow Provider(s)

microsoft-azure

Versions of Apache Airflow Providers

apache-airflow-providers-microsoft-azure==12.6.1

Apache Airflow version

3.0.6

Operating System

Linux

Deployment

Astronomer

Deployment details

No response

What happened

Running the AzureDataFactoryRunPipelineOperator async + Airflow 3.0.3 gives this failure:

ERROR - Task failed with exception: source="task"
AirflowException: You cannot use AsyncToSync in the same thread as an async event loop - just await the async function directly.
File "/usr/local/lib/python3.12/site-packages/airflow/sdk/execution_time/task_runner.py", line 920 in run
File "/usr/local/lib/python3.12/site-packages/airflow/sdk/execution_time/task_runner.py", line 1215 in _execute_task
File "/usr/local/lib/python3.12/site-packages/airflow/sdk/bases/operator.py", line 1606 in resume_execution
File "/usr/local/lib/python3.12/site-packages/airflow/providers/microsoft/azure/operators/data_factory.py", line 256 in execute_complete

The operator runs fine on Airflow 2.

What you think should happen instead

The operator should not fail

How to reproduce

Run AzureDataFactoryRunPipelineOperator async + Airflow 3.0.3 or higher

Anything else

Same error also found in other issues/PRs:

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. ashb commented on Sep 17, 2025

    @ashb
    Member

    L256 seems to be a raise AirflowException(event["message"]) -- is that really the line it's blowing up on and the end of the stack trace?

    Ohh. that is the error being propogated from the trigger, so it's got the wrong stack trace.

  2. ashb commented on Sep 17, 2025

    @ashb
    Member

    @BasPH Is there anything further up in the task logs from the trigger itself that might actually tell us the correct location?

  3. Vamsi-klu commented on Aug 27, 2026

    @Vamsi-klu
  4. added a commit that references this issue on Aug 29, 2026
    39b4804
  5. added a commit that references this issue on Sep 11, 2026
    89075ad
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions