Fabric Manged Airflow is not stable

[nerminyehia]

Hey,

I’m working on a POC to run dbt on Fabric Managed Airflow, but I’ve been running into several issues:

• Two days ago, the default Airflow version unexpectedly changed to 2.6.5, after which nothing worked properly. The next day, it reverted to 2.10.5.

• About two weeks ago, I successfully got it running with version 2.10.5 using specific requirements, but now the same setup no longer works — no schedulers show up, and Airflow isn’t able to start any tasks. (

  "astronomer-cosmos==1.10.1"

  "dbt-fabric==1.9.5". this setup was working properly 2 weeks back)
  Error stays for hours till the env is stopped (

  The scheduler does not appear to be running. Last heartbeat was received 29 seconds ago.

  The DAGs list may not update, and new tasks will not be scheduled.

  )

• I’m unable to restart the environment; it keeps timing out, so I have to recreate new environments each time.

Could you please let me know if there’s a timeline or plan to address these issues and stabilize the managed Airflow service?

Thanks,

Nermin

[v-veshwara-msft]

Hi @nerminyehia ,
Just wanted to check if the information shared by @Murtaza_Ghafoor  was helpful.

Please try the steps suggested. As mentioned, the recommended approach is to continue using the current setup until the Managed Airflow service is stabilized.

Please feel free to reach out if you have any further questions.

Thank you.

[V-yubandi-msft]

Hi @nerminyehia ,

I wanted to check if you had the opportunity to review the information provided by @Murtaza_Ghafoor . Please feel free to contact us if you have any further questions. 
 

Thank you and continue using Microsoft Fabric Community Forum.

[Murtaza_Ghafoor · Accepted solution]

Here’s a concise possible resolution:

• Use Airflow version 2.10.5 manually when creating the environment (avoid default).
• Reinstall dependencies in the requirements:
• astronomer-cosmos==1.10.1
• dbt-fabric==1.9.5
• Restart the environment from the Fabric portal after installation.
• If the scheduler still fails, delete and recreate the environment using a clean config.
• Microsoft is aware of intermittent version rollbacks — a stability fix is in progress, so keep the environment pinned to 2.10.5 until resolved.