Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
uyarasi
Frequent Visitor

Getting an error while refreshing power bi report

  • Data source error: The operation was throttled by Power BI Premium because there were too many datasets being processed concurrently. Please try again later.

Any ideas how to resolve this error?

1 ACCEPTED SOLUTION
PritamA
Frequent Visitor

you can only refresh 6 datasets concurrently. Any other datasets will have to wait in queue. The important part of the documentation is this:

Refreshes, like queries, require the model be loaded into memory. If there is insufficient memory, the Power BI service will attempt to evict inactive models, and if this is not possible (as all models are active), the refresh job is queued. Refreshes are typically CPU-intensive, even more so than queries. For this reason, there are capacity limits on the number of concurrent refreshes, set to 1.5 x the number of backend v-cores, rounded up. If there are too many concurrent refreshes, a scheduled refresh will be queued. When these situations occur, it takes longer for the refresh to complete. On-demand refreshes such as those triggered by a user request or an API call will retry three times [1]. If there still aren't enough resources, the refresh will then fail.

 

So to solve your issues, you'll want to have a look at the Premium Capacity Metrics App and look at other refreshes happening at the same time.

View solution in original post

2 REPLIES 2
PritamA
Frequent Visitor

you can only refresh 6 datasets concurrently. Any other datasets will have to wait in queue. The important part of the documentation is this:

Refreshes, like queries, require the model be loaded into memory. If there is insufficient memory, the Power BI service will attempt to evict inactive models, and if this is not possible (as all models are active), the refresh job is queued. Refreshes are typically CPU-intensive, even more so than queries. For this reason, there are capacity limits on the number of concurrent refreshes, set to 1.5 x the number of backend v-cores, rounded up. If there are too many concurrent refreshes, a scheduled refresh will be queued. When these situations occur, it takes longer for the refresh to complete. On-demand refreshes such as those triggered by a user request or an API call will retry three times [1]. If there still aren't enough resources, the refresh will then fail.

 

So to solve your issues, you'll want to have a look at the Premium Capacity Metrics App and look at other refreshes happening at the same time.

If you are on Premium Capacity Gen2, there is actually no cap on data refreshes. 
https://learn.microsoft.com/en-us/power-bi/enterprise/service-premium-gen2-what-is#refreshes

@uyarasi  Are you using PPU? or Premium Capacity?

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors