Paginated reports suddently randomly give the error "Something went wrong" when embedded

[massy]

We have many paginated reports embedded in different applications using Embedded license capacities.

Starting yesterday we have this error very often when we open one of the embedded reports from the applications:

Note that actually the report is embedded as you can see in the background, and if we click "Close" in the error window we are able to interact with it.

This is happening a lot of time (but not always) first time you open the application, then if you open another report generally it will work (but again not always, sometimes the error appears again).

This is suddently happening starting this week in different applications that use different Embedded capacities, in all environments we have.

In the Power BI Service everything is working fine.

Error details:

Activity ID: 67a5758b-e352-4521-aaf7-c33b81f78fe6
Request ID: cf8c6882-a2b0-71b7-6d02-86385810ff96
Correlation ID: d19d7f1b-e1f9-9107-62d5-c7cb48af71e6
Time: Tue Nov 05 2024 14:57:43 GMT+0100 (Central European Standard Time)
Service version: 13.0.24611.45
Client version: 2410.4.21630-train
Cluster URI: https://WABI-US-NORTH-CENTRAL-B-redirect.analysis.windows.net

[v-fenling-msft]

Hi, @massy 

We have seen on the internal platform that other engineers have reported this issue and submitted it.
The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.

I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Fen Ling,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[jojolapin2]

Hello,

Do you have any news on the fix for this issue please ? 

[jleroy-dev]

We're experiencing the same issue.

It doesn’t occur on all devices: my MacBook Pro (2024, M3 Pro) works fine, but my MacBook Pro (2015, i7) is affected. Our users on Windows are also encountering this issue.

It doesn’t appear to be network-related, as simulating a slow connection doesn’t affect the outcome.

Web: powerbi-client-angular@3.0.5
Client: Microsoft.PowerBI.Api@4.22.*