Couldn't load the data for this visual "Incorrect document syntax"

[DigitalHermit]

I get this error intermittently when making various slicer selections in the app.powerbi.com portal on a report. There were no errors on refresh. No idea how to workaround. This looks like could be another bug in power bi portal.

0x000000010x00000001Incorrect document syntax.

Please try again later or contact support. If you contact support, please provide these details.

Activity ID: ad44c2b6-1de6-4c20-945f-f3dcc8abee01
Request ID: 8698854d-4b24-4e98-b40b-586703382f37
Correlation ID: ab2defff-5201-1362-c388-554a49876e3d
Time: Mon Feb 13 2023 12:36:00 GMT-0500 (Eastern Standard Time)
Service version: 13.0.20053.53
Client version: 2302.1.12237-train
Cluster URI: https://wabi-us-north-central-b-redirect.analysis.windows.net/

[Anonymous]

Hi @DigitalHermit ,

I can't reproduce your issue.

Based on the above information, if you are a Power BI Pro licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

The link of Power BI Support: Support | Microsoft Power BI

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community

Best Regards,
Community Support Team _ Caitlyn

[Probleema]

I have encountered the same kind of problem on Power BI Service using Pro License. If I select around 20-30 values to a slicer then some slicers and visuals get this error message:

Couldn't load the data for this visual

Couldn't retrieve the data for this visual. Please try again later.
Please try again later or contact support. If you contact support, please provide these details

Http Status Code 429

I tried to get same error in Desktop but it works just fine. It also affects a report refreshed visual which comes from a different table that is not connected to other tables.

[Probleema]

I can get this to work again by waiting a few minutes and then try to use other working slicers. If I select a value on different slicer and switch it on and off then other slicer and visuals can recover from the errored state. After this I can select more values to the original slicer that caused the error. I can add a few more values until I encounter the same original error.