Forum Discussion
Power BI ExportToFile API – Concurrent Request Throttling (429 Errors) and Request for Workaround
- 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.
- 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.
Hi poojagh,
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to AnkitKukreja for sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solution? If so, please mark it as the solution. This will help other community members solve similar problems faster.
Thank you.
Hi v-ssriganesh ,
The query is still open and would like more insights on how this can be handled from a product point of view?
Any help here would be greatly apprecited!
- v-ssriganesh1 year agoCommunity Support
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.- v-ssriganesh1 year agoCommunity Support
Hi poojagh,
Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.
- poojagh1 year agoFrequent Visitor
Hi v-ssriganesh ,
The issue is still open