powerbi online kusto query execution error, but not able to repro locally.

[SooKuanTeo]

I've been receiving this error from Powerbi Online version once in a while. But I'm not able to repro it locally, tried many many time to refresh. Anyone experience this? Is there a way to find out exactly what query that cause this?

Failure details: Query execution has exceeded the allowed limits (80DA0003): Query result set has exceeded the internal data size limit 67108864 (E_QUERY_RESULT_SET_TOO_LARGE; see https://aka.ms/kustoquerylimits). [0]Kusto.Data.Exceptions.KustoServicePartialQueryFailureLimitsExceededException: Query execution has exceeded the allowed limits (80DA0003): Query result set has exceeded the internal data size limit 67108864 (E_QUERY_RESULT_SET_TOO_LARGE; see https://aka.ms/kustoquerylimits). Timestamp=2022-05-25T15:38:51.9282044Z ClientRequestId=KPBI;e322df19-db13-4623-99e0-9d062dd36586;f44b2dbc-4be7-4a52-b3dd-98a821c22345;3aad42f1-66e8-40b4-9be6-512e1a902d89 ActivityId=72dfc040-d9f7-45b3-8a73-25ff51550ac7 ActivityType=GW.Http.CallContext ServiceAlias=RDSPRODUS2 MachineName=KENGINE000027 ProcessName=Kusto.WinSvc.Svc ProcessId=11528 ThreadId=9848 AppDomainName=Kusto.WinSvc.Svc.exe ActivityStack=(Activity stack: CRID=KPBI;e322df19-db13-4623-99e0-9d062dd36586;f44b2dbc-4be7-4a52-b3dd-98a821c22345;3aad42f1-66e8-40b4-9be6-512e1a902d89 ARID=72dfc040-d9f7-45b3-8a73-25ff51550ac7 > GW.Http.CallContext/72dfc040-d9f7-45b3-8a73-25ff51550ac7) MonitoredActivityContext=(ActivityType=GW.Http.CallContext, Timestamp=2022-05-25T15:38:38.0680925Z, ParentActivityId=72dfc040-d9f7-45b3-8a73-25ff51550ac7, TimeSinceStarted=13860.1119 [ms])ErrorCode= ErrorReason= ErrorMessage= DataSource= DatabaseName= ClientRequestId= ActivityId=00000000-0000-0000-0000-000000000000 UnderlyingErrorCode=80DA0003 UnderlyingErrorMessage=Query result set has exceeded the internal data size limit 67108864 (E_QUERY_RESULT_SET_TOO_LARGE; see https://aka.ms/kustoquerylimits)

Technical Information

Activity Id:

74270bb2-feb3-4b0e-961b-9368ee2cee74

Request Id:

e322df19-db13-4623-99e0-9d062dd36586

Cluster Name:

DF-MSIT-SCUS-redirect.analysis.windows.net

Refresh Start Time:

May 25, 2022 15:03 UTC

Refresh End Time:

May 25, 2022 15:38 UTC

another instance:

Technical Information

Activity Id:

9fb17afa-ebaf-4eb4-b729-5ecddf42d66a

Request Id:

70b7dcdc-d7d1-46ab-ad55-0ccb7d89f7d0

Cluster Name:

DF-MSIT-SCUS-redirect.analysis.windows.net

Refresh Start Time:

May 25, 2022 13:03 UTC

Refresh End Time:

May 25, 2022 13:16 UTC

[v-yalanwu-msft · Accepted solution]

Hi, @SooKuanTeo ;

There are several strategies for dealing with this error.

• Reduce the result set size by modifying the query to only return interesting data. This strategy is useful when the initial failing query is too "wide". For example, the query doesn't project away data columns that aren't needed.
• Reduce the result set size by shifting post-query processing, such as aggregations, into the query itself. The strategy is useful in scenarios where the output of the query is fed to another processing system, and that then does other aggregations.
• Switch from queries to using data export when you want to export large sets of data from the service.
• Instruct the service to suppress this query limit using set statements listed below or flags in client request properties.

Generally speaking, when the limit set by default is exceeded, some of the exceeded queries will fail and display "Partial query failed".you can change the size of the default limit by setting truncationmaxsize and truncationmaxrecords to solve the problem of error reporting.

Here is the reference document link: Query limits - Azure Data Explorer | Microsoft Docs

Best Regards,
Community Support Team _ Yalan Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.