Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Any ideas how to resolve this error?
Solved! Go to Solution.
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.
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?
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
20 | |
19 | |
18 | |
15 | |
12 |
User | Count |
---|---|
34 | |
27 | |
25 | |
21 | |
19 |