Web content failed to get content error in Power BI

[mehalam]

Hi All,

We are importing ADX(kusto) dataset in Power BI using direct query mode.
Since we scaled up the cpu count in ADX, the visuals got crashed in Power BI desktop/Service and got the below error.

Web.Contents failed to get contents from 'https://(Clustername.location.)kusto.windows.net/v1/rest/query?db=(database)&csl=.show%20version' (520): InternalServiceError

But the query and tables are working fine in ADX, only in Power BI we are facing the issue.
For every refresh, Some of the visuals are working and some of the visuals are crashing.
Its soo weird and we can't recoginze the rootcause of this issue.

Even I tried to create a new Power BI report, i got the same issue with this ADX query.

@amitchandak @lbendlin @Daniel29195 @Ritaf1983  @Ahmedx  @amustafa @Ashish_Mathur @IrkenCR @v-stephen-msft Please help on this

[lbendlin]

Please confirm the error message. Is it 520 or 502?

[mehalam]

@lbendlin 520 it is

[amustafa]

Hi @mehalam Thank you for tagging me. Unfortunatly, I have never used ADX before but it seems like your query is more complex which cannot be replicated in Power Query so that's why you are using ADX. There's no good hits on same issue in the forums. I would check the complex query section in MS Learn doc link below or last resort is to open a ticket with MS Support.

Power Query Azure Data Explorer (Kusto) connector - Power Query | Microsoft Learn

[mehalam]

@amustafa we didn't use any complex query. just getting the single table (not using any query) from ADX through Direct query mode. 

And also once we scale down and return back to the previous state of cpu count. The reports are coming up and working fine.

Due to the performance issue, we are in need of scaling up the cpu count in ADX which results in crashing power bi reports. 

Need help to resolve this issue!

[lbendlin]

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .