Forum Discussion

poojagh's avatar
poojagh
Frequent Visitor
1 year ago
Solved

Power BI ExportToFile API – Concurrent Request Throttling (429 Errors) and Request for Workaround

Description: We are encountering throttling issues while using the Power BI exportToFile API, despite adhering to the documented limitations. According to the documentation: The exportToFile API...
  • AnkitKukreja's avatar
    1 year ago

    Hi! poojagh 

    • The 500 concurrent requests per capacity is a theoretical upper bound under ideal conditions.
    • In practice, effective limits can be much lower due to:
      • Report complexity (visuals, data volume, DAX calculations)
      • Capacity load (other workloads running)
      • Workspace or tenant-level constraints 

    Export Power BI embedded analytics paginated reports API - Power BI | Microsoft Learn

     

    • Microsoft applies dynamic throttling based on real-time capacity usage and system health.
    • Even if you're under the 500-request limit, you may be throttled if:
      • Your capacity is under heavy load.
      • You're using Premium Per User (PPU), which has stricter limits (e.g., 1 export every 5 minutes per user)

    Solved: Power BI Export to File API Rate Limitation - Microsoft Fabric Community

     

    I would advice you to raise a support ticket in case you need anything else on this.

     

     

  • v-ssriganesh's avatar
    v-ssriganesh
    1 year ago

    Hello poojagh,
    Thank you for the update.

    Given that you're still experiencing throttling issues even with fewer concurrent ExportToFile API requests than the documented limits, it's understandable that you'd want clarity from a product behavior standpoint.

    • The documented limit of 500 concurrent exports per capacity is a maximum theoretical threshold, assuming minimal capacity usage, lightweight reports, and no additional user or refresh loads.
    • The Power BI service dynamically adjusts throttling thresholds based on Capacity load (CPU/memory), Report complexity (DAX, visuals, pages), Backend resource availability and Platform stability

    This means 429 errors may be triggered earlier than expected, particularly during:

    • Sudden bursts of concurrent exports
    • Times of peak usage on the capacity
    • Heavy or inefficient report exports (e.g., long DAX chains, DirectQuery, high page count)

    To properly understand why you're encountering throttling below expected levels, we recommend opening a Microsoft support ticket for further investigation. You can explain all the troubleshooting steps you have taken to help them better understand the issue.

    You can create a Microsoft support ticket with the help of the link below:
    https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket


    If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
    Thank you.