Unable to load model due to reaching capacity limits Unable to open this report because your organization's compute capacity has exceeded its limits. Try again later. Please check the technical details for more information

Question

• Underlying ErrorCapacity operation failed with error code CapacityLimitExceeded
• Activity ID [moderator note: personal info removed]
• Correlation ID [moderator note: personal info removed]
• Request ID [moderator note: personal info removed]
• TimeFri Apr 17 2026 16:06:48 GMT-0400 (Eastern Daylight Time)
• Service version13.0.28141.25
• Client version2604.1.28665-train
• Cluster URI [moderator note: personal info removed]

Answer 1

Hi @Compton, Bobby, 

Thank you for reaching out regarding the technical difficulties you encountered. Based on the details provided, it appears that you are unable to load specific models or open reports due to a CapacityLimitExceeded error. This indicates that your organization's allocated compute resources have reached their current operational threshold, preventing the system from processing further requests at this time. 

To ensure you receive the most logical and effective resolution, I strongly recommend sharing this concern within both the Microsoft Power BI Forum and the Microsoft Power Platform Community. 

The context of this issue involves complex backend infrastructure and resource allocation that is specific to Power BI premium or fabric capacities. By engaging with these specialized communities, you gain direct access to: 

• Experts who specialize specifically in capacity management and performance tuning. 
• Community members and MVPs who have navigated similar organizational limit constraints and can provide proven optimization strategies. 
• More precise guidance on whether this requires a temporary cool down period or a permanent adjustment to your organization's capacity settings. 

I apologize for directing you to another community, but because the scope of this category is primarily focused on Microsoft 365, our knowledge of Power Apps and Power BI capacity management is limited. Guiding you to the most suitable resource will help you get faster and more accurate support. 

As a community moderator, I hope you understand that our access to internal development details is limited. I will continue to support you within the scope of my responsibilities and will always do my best to provide you with the best possible experience. 

I appreciate your patience and look forward to seeing your issue resolved through the expertise of the specialized support teams.

---

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 2

The error indicates that the Microsoft Fabric (or Power BI/Fabric) capacity hosting the report was overloaded at the time of access and entered a rejection phase (CapacityLimitExceeded). To resolve this, a Fabric capacity administrator must diagnose which workload caused the overload and then optimize or reschedule it, or increase capacity.

Use the three-stage troubleshooting process with the Microsoft Fabric Capacity Metrics app:

1. Confirm the capacity was overloaded at the error time
   1. Open the Microsoft Fabric Capacity Metrics app and go to the Compute page.
   2. Ensure the CU tab is selected in the Multimetric ribbon chart (top-left) and the System events tab is selected in the top-right visual so the System events table is visible.
   3. In the Multimetric ribbon chart, select the date matching the error time (for example, the day corresponding to Fri Apr 17 2026 16:06:48 GMT-0400). This filters all visuals to that day.
   4. In the System events table, look for entries where Capacity state changed to Overloaded with reason AllRejected, InteractiveDelay, or InteractiveRejected, followed later by Capacity state Active with reason NotOverloaded.
   5. Note the start and end times of the overload window (from the first Overloaded event to the subsequent Active event). During this interval, “capacity limit exceeded” errors can occur.
2. Check if throttling occurred during that overload
   1. On the same capacity in the Metrics app, switch to the Throttling tab on the Compute page.
   2. Review the charts for Interactive delay, Interactive rejection, and Background rejection.
   3. Focus on the chart type that matches the failing operation:
      • Report viewing/querying: interactive.
      • Refreshes, long-running jobs: background.
   4. Around the error time (within the overload window from stage 1), check whether any of these charts show values above 100%. Values above 100% confirm throttling (delays or rejections) occurred and align with the CapacityLimitExceeded error.
3. Identify the workspace and item causing the overload
   1. Still on the Compute page, use the Matrix by item (Items) table to see which workspaces, items, and operations consumed the most capacity during the overload window.
   2. Use the drill-through from the Compute page to open the Timepoint detail page for a timepoint within the overload interval.
   3. On the Timepoint detail page, review the lists of interactive and background operations running during that time and identify those consuming the largest share of capacity (for example, a semantic model refresh, a report, or a notebook).
   4. Note the Workspace, Item kind, and Item name of the top culprits. These are the items to optimize (e.g., model/query optimization), reschedule (e.g., move heavy refreshes away from peak interactive usage), or move to a larger capacity.

If the failing report depends on a semantic model in another workspace on a different capacity, repeat the same analysis on that other capacity for the same timeframe.

Once the heavy workloads are optimized or rescheduled, or capacity is increased, the “Unable to load model due to reaching capacity limits” and CapacityLimitExceeded errors should stop occurring for that report.

---

References:

• Troubleshooting guide: Diagnose and resolve "capacity limit exceeded" errors