Power BI Service Visual Load Issue

[Quiny_Harl]

Hi folks,

Some users of my report are experiencing a visual load issue:

The erros are:
"More details: The XML for Analysis request timed out before it was completed. Timeout value: 225 sec."
as well as "Error from Bulk Filtering" from the bulk slicers.
I've read the other posts with similar issues, but none of them provided a solution to my case.
This report has been live for years in a Premium capacity workspace with hundreds of users using it daily. No changes have been done recently. Only a fraction of the users are facing this issue since two days ago. For the rest, everything is working fine.
Changing data model and measures is not an option because it is a big complex report with many measures that's been working fine until this week. Redeveloping it is out of the current scope.
Any help is appreaciated!

[Anonymous]

Hi @Quiny_Harl ,
Yes, this is a known issue and the Power Bi team is working on fixing this. I will update here once there is any progress.

Best Regards,

Ada Wang

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

[Quiny_Harl]

@Anonymous, then if it is a know issue why is it not included in the Fabric known issues?

[Anonymous]

Hi @Quiny_Harl ,

Thank you for bringing this to my attention. I understand that you are concerned about not seeing the issue in the Fabric known issue list. However, it is important to note that not all known issues are listed in the Fabric known issue list. There may be various reasons for this, such as the issue being under investigation or in the process of being resolved. I hope this clarifies the situation for you. Please let me know if you have any further questions or concerns.

Best Regards,

Ada Wang

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

[Quiny_Harl]

@Anonymous Any update on this, please?

[Quiny_Harl]

@Anonymous, it would be good if this issue is listed there! Unless Power BI team is not resolving it in the next couple of hours. Just in our case it affects many users and creates a huge problem for which we don't have a solution. You can see how "someone in fabric community chat told me there is a bug" is not plausible excuse to give to the business when they are expecting either a solution or at least a good explanation of why they can't have their reports.
Also, can you please give me a timeline on when it is expected to have this bug fixed?

[Anonymous]

Hi @Quiny_Harl ,

The incident has been referred to the other team for further investigation. We are working on this and let you know once issue is solved.

Best Regards,

Ada Wang

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

[Quiny_Harl]

@Anonymous Thanks for the info (although I don't understand it). We will be waiting for futher update. In the meantime, would it be possible to include this bug in the Fabric known issues?
It would have saved us a lot of nerves, time and effort, if we knew earlier that this is a global issue.

[Anonymous]

Hi @Quiny_Harl ,

The Power BI team is working hard to resolve the issues found. Please be patient as I will update here once there are any new developments on this issue.

Best Regards,

Ada Wang

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

[Quiny_Harl]

@Anonymous , I'm sorry but I had to decline to mark this answer as a solution because "Power BI team is working hard" is not really a solution. Especially when it takes the Power BI team a month to resolve this issue while dozens of users are affected ONLY in our company.
In that regard, do you have any update on it?

[hvanlint]

Any news here? We're experiencing the same issue.

We have several users reporting the "operation cancelled by the user" problem.

[Anonymous]

Hi @Quiny_Harl ,

We have reported this issue and submitted it to the product team.
They have been aware of the issue and the engineers will do their best to resolve it. I will update here if there is any progress, so please be patient. 

Best Regards,

Ada Wang

[Quiny_Harl]

@Anonymous, 
What do you mean by "they have been aware of the issue"? Does this mean that this is a global Power BI Service problem?
FYI, users are also experiencing another type of error where the error message says "Operation cancelled by user".
Sometimes, when a user opens a report page, the visuals would load normally but then when they click on any slicer, that slicer immediatelly turns into an error, even before any selection was made.
I've removed all unused columns from the report and reduced the size to 800MB. I've published the report to another premium workspace. Nevertheless, some users keep experiencing the same issue.

[Anonymous]

Hi @Quiny_Harl ,

Thanks @lbendlin  for giving advice on troubleshooting the problem, I need to gather more information to confirm if what you are experiencing is a known issue:

1. Please provide your version of Power Bi Desktop.
2. Is your report visual objects not loading for users intermittent or persistent.
3. Are only certain users unable to view the visual objects? Does it start working when they refresh their browser and view the report again.

Best Regards,

Ada Wang

[Quiny_Harl]

Hi @Anonymous,

1. My Power BI Desktop version is December 2023
2. It is intermittent - users would have this error on certain visuals, next time they would have it on other visuals and sometimes they wouldn't have it at all.
3. Only a fraction of all users are experiencing this issue. Most of them are based in the same country. Refreshing browser, clearing browser cache, trying different browser - all these do NOT have an effect on this problem.

I also tried publishing a copy of the report to Power BI Service with a different name (in order to change the report & dataset link) but this didn't work as well. The premium workspace capacity also seems to be sufficient.

[lbendlin]

Have the users try in Incognito mode.

[Quiny_Harl]

Would you please elaborate on how is that going to help solve the issue?

[lbendlin]

This will allow you to see if the errors are reproducible or if they are caused by a stuck cache.

[Quiny_Harl]

Thank you for the suggestion. We tested it - cleared the browser cache and also tried with another browser - but it didn't help.