Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I'm encountering in this while i open my report in power bi service, do you have any suggestion? Thanks
Number of resources exceeded
The query exceeded the number of available resources. Try applying a filter to reduce the amount of data requested.
Try again later or contact support with the following information
Solved! Go to Solution.
Please refer this thread,
Hi @Simomazzi
Just checking in one last time. Were you able to try out any of the suggestions shared earlier? If your issue is resolved, marking the accepted solution would be a big help to others who might be facing the same scenario.
If you went in a different direction or still need support, feel free to drop a quick update, we’re happy to keep helping.
Regards,
Akhil.
Hi @Simomazzi
Just checking in to see if the solution shared by super users worked for you? If you're still facing any issues or need more help, feel free to let us know, we're happy to assist further.
If the response helped resolve your issue, please consider marking it as Accepted as Solution and give it a thumbs up if you found it helpful.
Thanks,
Akhil.
Thank you for addresing the issue @Poojara_D12 @collinq @BhavinVyas3003
Hi @Simomazzi
we would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Regards,
Akhil
Hi @Simomazzi
The error message “Number of resources exceeded” in Power BI Service typically indicates that your query has demanded more compute resources than what’s available to your workspace at that moment, either due to excessive memory usage, long-running DAX queries, or large result sets. This is especially common in complex reports that query large volumes of data, use many visuals loading at once, or involve high-cardinality fields. If you're using shared capacity, the limits are more restrictive, and resource contention with other tenants can worsen the issue. On Fabric or Premium capacity, although limits are higher, heavy queries can still trigger this if the dataset isn't optimized. To resolve this, consider applying report-level or visual-level filters to reduce the data being queried. Also, review your DAX measures and model structure to ensure there are no overly expensive calculations. If your dataset is in DirectQuery mode, evaluate whether Import mode or aggregations could improve performance. As a longer-term solution, you may also explore breaking large reports into smaller, more focused pages or separating them by user roles or business needs. If the issue persists and you're on dedicated capacity, your capacity admin can check usage metrics and consider scaling up resources or tuning workloads through the Fabric capacity settings.
Hey @Simomazzi ,
You may see if you can filter down the amount of data. And, see when you get to the point where it does work. You may also just need to reduce the number of columns in the visual to see if it is one column in particular that is causing an issue.
Proud to be a Datanaut!
Private message me for consulting or training needs.
Please refer this thread,