DEV Fabric Workspace Refresh Failure

Hi manoj_0911 

This is a refresh-time memory limit issue in Fabric F8, not a report-rendering issue.
Even though the semantic model loads and reports work, the incremental refresh operation can still exceed the memory available for processing partitions.

In your case, the key clue is:

• Consumed memory = 2637 MB
• Memory limit = 2637 MB

That means refresh hit the capacity guardrail exactly and was canceled.

What to do

1) Make sure query folding is preserved

For Incremental Refresh to work efficiently, Power Query must push the date filter down to Athena.

If folding breaks, Power BI may pull too much data into memory during refresh.

Action

• Verify the UPDATE_DATETIME filter is applied as early as possible in Power Query
• Avoid transformations before the filter that break folding
• Check whether Athena is actually receiving the filtered query

Microsoft docs

• Incremental refresh overview:
  https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-overview
• Incremental refresh troubleshooting:
  https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-troubleshoot

2) Reduce the amount of data processed per refresh

If the refresh window is too large, or too many partitions are being reprocessed, memory usage will spike.

Action

• Reduce the refresh period if possible
• Keep only the required historical range
• Reprocess fewer partitions at a time if you are managing partitions manually

3) Remove unused and high-cardinality columns

Model width is one of the biggest causes of refresh memory pressure.

Action

• Remove columns not used in reports, relationships, or DAX
• Reduce high-cardinality text columns
• Replace long text or GUIDs with integer keys where possible
• Convert datetimes to dates if time precision is not needed

Microsoft docs

• Import modeling data reduction:
  https://learn.microsoft.com/en-us/power-bi/guidance/import-modeling-data-reduction

4) Simplify Power Query transformations

Heavy M transformations increase refresh overhead and may break folding.

Action

• Move shaping work upstream if possible
• Keep Power Query steps minimal
• Filter early, remove columns early, and avoid expensive custom logic in the semantic model

5) Check capacity headroom

An F8 capacity is relatively small for import refresh workloads.

Action

• Use the Fabric Capacity Metrics App to see whether the refresh is pushing the capacity to its limit
• If the model is close to the limit, consider scaling up the capacity or reducing model size

Recommended interpretation

For Fabric F8, this behavior is not unusual when:

• the table is large,
• the refresh window is broad,
• folding is imperfect,
• or the model has many wide/high-cardinality columns.

So the likely fix is either:

1. optimize the model and refresh pattern, or
2. move to a larger Fabric capacity
   

Some more microsoft documentation links for your reference :

• Incremental refresh overview:
  https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-overview

• Incremental refresh troubleshooting:
  https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-troubleshoot

• Data reduction guidance for import models:
  https://learn.microsoft.com/en-us/power-bi/guidance/import-modeling-data-reduction

• Refresh troubleshooting scenarios:
  https://learn.microsoft.com/en-us/power-bi/connect-data/refresh-troubleshooting-refresh-scenarios