Unable to Access Airflow - 503 Service Temporarily Unavailable

[angela_n]

Hi everyone,

I’ve been facing an issue with Airflow since Friday. Every time I try to access it, I’m met with a “503 Service Temporarily Unavailable” error. This means I can’t view my DAGs or check the status of any runs.

Has anyone else encountered this issue, or does anyone have suggestions on how to resolve it?

Thanks

Angela

[angela_n · Accepted solution]

Unfortunately, the current limitations on Microsoft Fabric Airflow led us to install our own version of Airflow and which is now running smoothly. 

When Airflow becomes a production-ready feature of fabric, we plan to reassess the transition to Fabric.  

[v-prasare]

Hi, We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.

Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

[v-prasare]

Hi @angela_n,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

Thanks,

Prashanth Are

MS Fabric community support

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query

[v-prasare]

Hi @angela_n , 

In this scenario i suggest you to raise a support ticket here. so, that they can assit you in addressing the issue you are facing. please follow below link on how to raise a support ticket:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thanks,

Prashanth

[angela_n]

An Update, After removing the Azure Devops synchronization, Airflow successfully loaded, adn the DAGs are now utilizing Fabric storage. 

However, Airflow is showing DAGs that are not present in Fabric.

The struture of the Azure Devops project is:

that matches the documentation. Any help with this issue is really appreciated. 

thanks, 

[v-prasare]

If this works fine, can you please mark your post as a solution. this will help other community memebers with similar questions find answers quickly

Thanks,

Prashanth Are