Resource Governer - Query uses more memory than the configured limit

[stan_w_gifford]

Good morning/afternoon all.

I have 11 users with the PBI Pro License (Including myself).

I have a report published and one page causes the error (listed below) on all users EXCEPT myself!

I am at a bit of a loss explaining why I can see the report however noone else can!

The error reported is:

More details: Resource Governing: This query uses more memory than the configured limit. The query — or calculations referenced by it — might be too memory-intensive to run. Either simplify the query or its calculations, or if using Power BI Premium, you may reach out to your capacity administrator to see if they can increase the per-query memory limit. More details: consumed memory 1331 MB, memory limit 1331 MB. See https://go.microsoft.com/fwlink/?linkid=2159752 to learn more.

Activity ID: abd68db3-cf32-4043-a3f0-9115a7911414

Correlation ID: 1d9a4077-7bf0-4f30-a409-99e9d6c7b891

Request ID: b7929fca-5d92-4ef1-83ef-56b66879b3a6

Time: Mon May 12 2025 12:46:17 GMT+1000 (Australian Eastern Standard Time)

Service version: 13.0.25874.35

Client version: 2505.1.24125-train

Cluster URI: https://wabi-australia-southeast-redirect.analysis.windows.net/

[stan_w_gifford · Accepted solution]

OK - I have fixed the report - still cannot fully explain why it worked on my system but not others.

Issue 1. For some reason, the schema/relationships were completely messed up - the report is based on Dynamics 365 data (CRM) and some joins made no sense - for example linking a sales order to contact from priority field in sales order to contact id...........

Fixing up the relationships did not fix the issue - but made me feel better.

Issue 2. After studying the page with issues (Note that I was finally able to duplicate issue using PBI desktop), managed to correlate the issue to the number of rows on the report. Added a new slicer and this finally resolved the issue.

Issue 3. I turned off Q&A in the Semantic model - my users would never use this and I am sure that the option would consume resource.

Stan

[Akash_Varuna]

HI @stan_w_gifford It might be because the query exceeds the memory limit configured for shared or Premium capacity, triggered by complex visuals or calculations. To fix this, simplify DAX expressions, aggregate data in Power Query, and streamline visuals to reduce memory usage. If you're on Premium, ask the admin to increase the per-query memory limit in the Admin Portal.