Power Query Refresh Issue Recurring After Update

Question

Power Query Refresh Issue Recurring After Update in August 2025.

The power query that I have created and been using for years keep promting this when I do my refresh " The query did not run or the Data Model could not be accessed.
Here's the effor message we got : Query optimizer generaed too many subcubes in the query plan.

I try to remove all the relationship but sill not able to refresh.

I need help.

Answer 1

Hello, good day and thanks for question. You may direct this to our neighbor community that is dedicated to PowerAutomate at https://community.powerplatform.com/forums/thread/?groupid=46ce02a3-e1a7-4176-81fc-d93a4001d287.

Answer 2

Hello soh judith

Welcome to Microsoft Q&A Forum.

I understand that your Power Query has been working well for years, but after the August 2025 update. it now fails to refresh.

Please don't be worried, here are some steps that you can kindly follow to help resolve this issue:

1. Simplify or Break Down the query:
   • Split a large, monolithic query into smaller, modular steps or intermediate queries.
   • Create intermediate queries to break transformations into manageable parts.
2. Review and refine applied steps:
   • Open the Advanced Editor and inspect the M code.
   • Look for deeply nested functions and chained steps - flatten or break them out as needed.
3. Optimized Data Model Usage:
   • Limit loading to only necessary columns or rows.
   • Use filters early in the query to reduce the volume of data processed.
   • If you've loaded to the Data Mode, try:
   • Enabling fast data load only for required tables.
   • Applying incremental refresh when working with large datasets.
4. Update and Repair Office Installation:
   • Ensure Office and Power Query components are up to date - sometimes updates introduce regressions that are later patched.
   • Repair your Office installation via Control Panel > Programs > Microsoft Office > Change > Quick Repair.
5. Clear Cache and Refresh:
   • Go to Data > Get Data > Query Options > Data Load > Clear All Caches, then retry refresh.
6. Use diagnostic tools:
   • Enable Power Query tracing (Options > Diagnostics > Enable tracing) and examine the logs for detailed failures

If the problem still persists, submit a support ticket directly to Microsoft, including diagnostics and query trace logs via Microsoft | Contact Us

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Answer 3

Hi soh judith

Is there any update on this thread?  

If the issue has been resolved, please mark the helpful replies as answers.  

This helps others in the community facing similar problems.  

Thanks for your understanding. 

Answer 4

Hi soh judith

You can also kindly try these steps to see if the issue is resolved or not:

1. Turn off Grand Totals and Subtotals in your PivotTable. These alone can trigger massive query complexity
2. Remove complex hierarchies from Rows/Columns - keep only necessary fields visible.
3. Confirm the Pivot is nit implicitly using .AllMember for hierarchies, especially when calculated members are present, as this can create inefficient MDX queries.

Let me know if this works, thank you for your time.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Answer 5

in my case Turn off Grand Totals and Subtotals helped