Hi @pablo_arc.
I’m not completely sure, but this error usually points to Power Query evaluator concurrency limits rather than a broken semantic model. In practice, it tends to happen when too many queries/entities are being evaluated at once during refresh (sometimes across other dataflows/models running under the same account as well). I’d first check whether any other refreshes are overlapping, then try to reduce the refresh workload (query folding, fewer intermediate queries, disabling load on staging queries, incremental refresh), and stagger schedules a bit. If this started suddenly without changes on your side, it may also be worth opening a support ticket and sharing the Activity ID + UTC timestamp, because there have been similar service-side incidents reported by others.
My suggestion is to consider these checks, in this order:
-
Check for overlapping refreshes
If other semantic models, dataflows, pipelines, or Power Automate flows are refreshing at the same time, they can consume the same evaluator pool. There are community reports showing the limit behaves per user/account context across workspaces, not simply per workspace.
[community....rosoft.com]
-
Reduce how much Power Query has to evaluate during refresh
This is often the most effective fix:
- keep query folding as far downstream as possible
- remove unnecessary intermediate referenced queries
- disable load for staging/helper queries
- avoid expensive row-by-row transformations early in the query
- avoid repeated merges/expands against large tables when they can be pushed to source
- if the model is large, use incremental refresh so fewer partitions/tables are processed on each run
If this response was helpful in any way, I’d gladly accept a kudo.
Please mark it as the correct solution. It helps other community members find their way faster.
Connect with me on LinkedIn
