Intensive use: will be tried again soon

[Syndicate_Admin]

I have my reports published on the web in a slower way. Previously, these had a fluency when performing the filters, but since the last update I gave it, this one takes a long time and I get a message called:

Intensive use: will be tried again soon.This report has surpassed the usage that is allowed at the same time. Try opening it later.

Is there a solution to this problem? It should be noted that nothing moved. Only the PBIX was updated and published on the web as a custom

[ejhonnatan0922]

Hi all.

The error continues, I have purchased the premium license per user and it does not work

[Ricape85]

Hola a Todos;

ya revise varias soluciones y el problema continua, por favor nos confirman si la falla es a nivel de servicio. Gracias

[Syndicate_Admin]

Hello.

It doesn't work, already change the license to premium per user and the same error follows.

[Syndicate_Admin]

Hello everyone.

Today I get the same error and it had never happened to me, is it possible that a generalized error is being generated?

[Syndicate_Admin]

The same thing happens to me, does it seem general?

[Syndicate_Admin]

Write in this forum thread that I have created

https://community.fabric.microsoft.com/t5/Service/Utilizaci%C3%B3n-intensiva-se-volver%C3%A1-a-inten...

[Syndicate_Admin]

Apparently yes.

[Ritaf1983 · Accepted solution]

Hi @Syndicate_Admin 

The message you're seeing, "Intensive use: will be tried again soon. This report has surpassed the usage that is allowed at the same time," indicates that your report has hit a usage limit on the Power BI web service, likely due to high traffic or the complexity of the report after the recent update.

Here are a few potential solutions to address this issue:

1. Optimize the Report Performance

Since the issue appeared after the update, there could be performance-heavy changes in the updated report. Here are a few steps to optimize:

• Optimize DAX queries: Review your DAX queries to ensure they are efficient. Avoid complex, nested calculations or calculations that can be pre-aggregated.
• Minimize the use of real-time visuals: Ensure you're not using too many real-time visuals or highly interactive elements that cause frequent recalculations.
• Reduce data volume: If possible, reduce the data being queried or displayed in your report. For example, consider using data aggregation or filters to limit the dataset size.

2. Enable Incremental Refresh

If the dataset is large and constantly growing, consider enabling incremental refresh. This will improve the performance by only refreshing the new or changed data rather than the entire dataset.

3. Check Your Power BI Service Capacity

The error could also indicate that your Power BI tenant is hitting its capacity limits (especially in a shared workspace or Power BI Pro environment):

• Review service limits: Check if the workspace or environment where your report is published has exceeded its resource or memory limits. Power BI service has usage caps for Pro users, which could be the issue.
• Consider upgrading to Power BI Premium: If the usage demand is high and frequent, upgrading to Power BI Premium could provide additional resources and capacity for concurrent usage.

4. Check the Data Source

Ensure the data source is not causing delays. If the source is slow or has higher latency (especially with large datasets or cloud services), this can impact performance.

5. Review Changes in the PBIX File

Even though "nothing moved," any changes in the PBIX file can have performance impacts. Consider reviewing:

• New measures, columns, or visual elements that might be heavier in terms of calculations.
• Custom visuals: If you added any custom visuals, they might be less optimized compared to native visuals.

6. Monitor Report Usage and Refresh Schedule

If your report is being used by many users at the same time, check your usage metrics to see if there are spikes in concurrent usage that coincide with the performance issues. Also, review your refresh schedule to avoid overlaps with peak usage times.

7. Use DirectQuery or Aggregations

If your data is large and loading times are too slow, you can explore using DirectQuery (if not already used) or aggregations to load only necessary data and improve performance.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

[Syndicate_Admin]

The error continues, new people are appearing with said incident today.

You can help us validate at a higher level.

Thank you