Hi naveenanda_vam ,

This error indicates that a subscription in Power BI experienced issues due to resource constraints while rendering the visuals for the report. Here’s how you can troubleshoot and resolve the problem effectively:

Root Cause

1. Resource Exceeded Error: The query associated with one or more visuals exceeded the resources available for rendering. This could be due to:

   • Large datasets being queried.
   • Inefficient data models or measures (DAX code).
   • Excessive complexity in visuals.

2. Timeout Error: The report query exceeded the 225-second timeout limit in Power BI Service. While it may still render in Power BI Desktop, the Power BI Service has stricter time and resource constraints.

Solutions

1. Optimize the Data Model

• Reduce Data Volume: Use filters or aggregates in your data model to reduce the size of data being queried.
• Remove Unnecessary Columns or Tables: Remove fields or tables that are not used in the visuals.
• Pre-Aggregate Data: Instead of calculating aggregations dynamically in Power BI, pre-calculate them in your data source or ETL process.

2. Optimize DAX Queries

• Review and optimize the DAX calculations in your report to ensure they are efficient.
• Avoid using heavy functions like SUMX, FILTER, and EARLIER unnecessarily.
• Replace complex calculated columns or tables with measures if possible.

3. Simplify the Visuals

• Reduce the Number of Visuals: Limit the number of visuals on a single page, as each visual executes a separate query.
• Simplify Visuals: Avoid complex visuals like maps or charts with many data points.
• Optimize Visual-Level Filters: Apply filters directly on visuals to limit the data scope.

4. Paginated Reports (if applicable)

• If you are using a paginated report, ensure that the report layout and data scope are minimal.
• Use parameters to filter the dataset before rendering.

5. Increase Capacity (Premium Workspaces)

• If you’re on a Power BI Premium workspace, consider increasing the capacity or scaling up the node (e.g., from P1 to P2).
• Check the workspace’s resource usage metrics to see if it's consistently reaching its limits.

6. Scheduled Refresh Optimization

• Ensure the data refresh process for the dataset completes successfully before the subscription triggers.
• Use dataflows to pre-process data and reduce query load on the dataset.

7. Adjust the Query Timeout

• For DirectQuery or Live Connection models, consider optimizing the underlying data source or reducing the complexity of queries to prevent timeouts.

8. Subscription Retry

• Delete the subscription and recreate it with the same configuration.
• Use the Test Email option to verify functionality.

Next Steps

1. Check Resource Metrics:

   • Go to Admin Portal > Capacity Settings (for Premium workspaces).
   • Review CPU and memory usage to identify bottlenecks.

2. Test in Power BI Desktop:

   • Refresh the visuals locally to verify if they execute without errors.
   • Check the Performance Analyzer in Power BI Desktop for slow visuals or queries.

3. Report the Issue (if unresolved):

   • If the issue persists despite optimization, report it to Power BI Support.
   • Share the Activity ID, Request ID, and Cluster Name from the error message for quicker resolution.

Immediate Workaround

• Reduce the data scope using report-level filters or slicers for the affected subscription page. This will decrease query complexity and help the subscription succeed in the short term.

Let me know if you need specific guidance on optimizing your DAX or model!

Please mark this as solution if it helps. Appreciate Kudos.