Hi @spindlerm ,
Thank you for posting query in Microsoft Q&A Platform.
Yes Looks like its because of
Limit execution timeout
.
By default, timeout is set to four minutes for queries, and 10 minutes for control commands. This value can be increased if needed (capped at one hour).
Below are the ways to increase timeout limit.
- Various client tools support changing the timeout as part of their global or per-connection settings. For example, in Kusto.Explorer, use Tools > Options* > Connections > Query Server Timeout.
- Programmatically, SDKs support setting the timeout through the
servertimeout
property. For example, in .NET SDK this is done through a client request property, by setting a value of typeSystem.TimeSpan
.
Click here to know more about this limit.
There are couple of other query limits also there in Kusto. You may end up facing them too. Please check below documentation with all details and steps to overcome.
https://learn.microsoft.com/en-us/azure/data-explorer/kusto/concepts/querylimits
Hope this helps. Please let us know if any further queries.
Please consider hitting Accept Answer
. Accepted answers help community as well.