cancel
Showing results for 
Search instead for 
Did you mean: 
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
PBI Sept Update Carousel

Power BI September 2023 Update

Take a look at the September 2023 Power BI update to learn more.

Learn Live

Learn Live: Event Series

Join Microsoft Reactor and learn from developers.

Dashboard in a day with date

Exclusive opportunity for Women!

Join us for a free, hands-on Microsoft workshop led by women trainers for women where you will learn how to build a Dashboard in a Day!

Top Solution Authors
Top Kudoed Authors