Get Error in Service

[Sonagupta]

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: d8892d22-556e-46e4-a3ad-8674b42940c8
Correlation ID: c38b39b6-fd17-e30f-eb22-52415d9cc2b2
Request ID: c6e73234-dfed-49e5-8e93-90cb0aeff03a
Time: Tue Jul 01 2025 12:52:22 GMT+0530 (India Standard Time)
Service version: 13.0.26187.35
Client version: 2506.4.24725-train
Cluster URI: https://wabi-india-west-redirect.analysis.windows.net/

i have short the dax for that Visual but still not get resolve this. Error comes when i publish the dashboard in service. 

using Pro license.

[v-pnaroju-msft]

Hi Sonagupta,

We are following up to see if your query has been resolved. Should you have identified a solution, we kindly request you to share it with the community to assist others facing similar issues.

If our response was helpful, please mark it as the accepted solution, as this helps the broader community.
Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Hi Sonagupta,

We are checking in to know if the information we provided helped in resolving your issue.
If you have any further questions, please do not hesitate to contact the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Hi Sonagupta,

We are following up to check if the information we shared helped to solve your problem.
If you have any more questions, please feel free to contact the Microsoft Fabric community.

Thank you.

[V-yubandi-msft]

Hi @Sonagupta ,

Thank you for the clear explanation @Poojara_D12 , it really helped understand the root cause more clearly. I’d like to share a few additional suggestions.

1. Consider breaking large visuals into smaller ones or using fewer fields, as this can improve performance.

2.  When writing DAX, try to avoid memory intensive functions like SUMX and FILTER where possible optimizing these can be beneficial.

3. Aggregating data before loading it into Power BI and using summarized tables instead of full transactional data can help reduce the load.

4. Tools such as Performance Analyzer and DAX Studio are useful for identifying which queries are using the most memory.

If the report is business critical and still exceeds Pro memory limits, consider exploring Premium capacity (F SKU), which offers a higher and adjustable memory limit per query.

— Yugandhar
Community Support Team.

[Poojara_D12 · Accepted solution]

Hi @Sonagupta 

The error you're encountering in Power BI Service — "Resource Governing: This query uses more memory than the configured limit" — indicates that the visual or its underlying DAX query is exceeding the per-query memory limit allowed by your current license tier, which is Power BI Pro. In Pro, the memory and CPU resources allocated for dataset processing and visual rendering are more constrained compared to Power BI Premium. Despite your efforts to simplify the DAX for the visual, it's likely that the combination of data volume, relationships, calculated columns/measures, or visuals themselves still leads to high memory usage (in your case, 1,331 MB, which hits the exact memory ceiling for a Pro environment).

This issue typically doesn’t occur in Power BI Desktop because the desktop version uses your local machine’s resources without the same memory throttling. But once published to the Power BI Service, queries are governed based on your tenant’s capacity tier.

To resolve this:

1. Simplify the visual: Reduce the number of fields, complex measures, or visual filters.

2. Avoid complex calculated columns/measures especially ones using iterators like

   SUMX, FILTER, or nested IF conditions.

3. Reduce data granularity: Use aggregations or summarized tables instead of detailed data.

4. Optimize the model: Remove unnecessary columns, relationships, or hidden fields that increase model size and complexity.

Since you are on Pro, and not Premium, you cannot increase the memory limits. If the report must run in its current state, consider moving the workspace to a Power BI Premium capacity (P SKU or F SKU in Fabric), where the per-query memory limit is higher and adjustable by an admin.

For now, use tools like Performance Analyzer in Power BI Desktop and DAX Studio to find the most expensive queries/measures, and reduce their memory footprint.