Forum Discussion

angela_n's avatar
angela_n
Frequent Visitor
8 months ago
Solved

Unable to create airflow job

Hello Community,

 

Since yesterday, I have been trying to create an Airflow job, and I keep getting this error:

 

{"message"."Request failed with 500(Internal Server Error): {\"error\":
{\"code\":\"RequestExecutionFailed\"\"pbi.error\":{\"code\":\"RequestExecutionFailed\"}}},
\nrequestid: 3ef3ae54-33f0-7abe-0149-28b28cc70fb1"}

 

I tried in different workspaces, and I get the same error. 

 

I am trying to test if you can trigger an Airflow DAG using the Aiflow API. 

 

Thanks, 

 

Ang

6 Replies

  • Hi angela_n, first check if you capacity region is with the Airflow region availability. If your region is not in the list, that might be the cause of the error.

     

    And as mentioned in this similar post, it might be just a temporary glitch and it might be suddenly working tomorrow.

     

    Hope this helps. If so, please give a Kudos 👍 or mark as Accepted Solution ✔️.

    • angela_n's avatar
      angela_n
      Frequent Visitor

      Hi nielsvdc 

       

      My capacity is East US, which is listed as supported.

      I also tried re-logging in, using a different browser, and clearing the cache, but I'm still getting the same message. At this point, it seems like a platform issue on Microsoft's side.

      If this is indeed a known glitch, I'm wondering why it's not reflected on the Service Health page, since everything currently shows as green.

      Given that the UI isn't working, I also attempted to create the Airflow job via Terraform. After waiting almost 10 minutes, the operation failed with the error "Context deadline exceeded."

      Let me know if there's any update or workaround I may have missed.

      Thanks

      • nielsvdc's avatar
        nielsvdc
        Super User

        It's working in my region, West Europe. Maybe create a support ticket with Microsoft to see if they can help you solve your problem. Fabric Support

         

        Hope this helps. If so, please give kudos 👍 and mark as Accepted Solution ✔️ to help others.

  • Hello angela_n,

     

    Since Apache Airflow in Fabric is a managed service that requires specific backend provisioning, a 500 error usually implies the service failed to allocate the necessary compute resources or containers for your instance.

     

    This is often caused by one of three things:

    • Region unavailability: New feature, so Apache Airflow Jobs are not yet available in all Azure regions where Fabric is deployed.

    • Tenant Setting Restrictions: The feature is disabled at the Tenant level, in preview.

    • Verify Capacity Assignment : Airflow Jobs require a genuine Fabric Capacity (F-SKU) or a Trial capacity. Not possible on Power BI Pro or PPU.

     

    References

    https://learn.microsoft.com/en-us/fabric/data-factory/apache-airflow-jobs-concepts

    https://learn.microsoft.com/en-us/fabric/data-factory/create-apache-airflow-jobs

     

    Hope it can help you!

    Best regards,

    Antoine

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi angela_n ,

    Thank you for reaching out to the Microsoft Fabric Community Forum.

     

    Could you please let us know if the issue has been resolved? I wanted to check if you had the opportunity to review the information provided by AntoineW . If that does not resolev your issue please raise a support ticket with microsoft as mentioned by nielsvdc . If you still require support, please let us know, we are happy to assist you.

     

    Thank you.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi angela_n ,

     

    We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
    If you still require support, please let us know, we are happy to assist you.

     

    Thank you.