Sudden Netherite "Client request timed out" exception about durabletask-netherite

[thegrekle]

Here's the full stack trace in case that's helpful.

Error: The operation failed with an unexpected status code: 500. Details: {"Message":"Something went wrong while processing your request","ExceptionMessage":"Client request timed out.","ExceptionType":"System.TimeoutException","StackTrace":"   at DurableTask.Netherite.Client.CreateTaskOrchestrationAsync(UInt32 partitionId, TaskMessage creationMessage, OrchestrationStatus[] dedupeStatuses) in /_/src/DurableTask.Netherite/OrchestrationService/Client.cs:line 469\r\n   at DurableTask.Netherite.NetheriteOrchestrationService.DurableTask.Core.IOrchestrationServiceClient.CreateTaskOrchestrationAsync(TaskMessage creationMessage, OrchestrationStatus[] dedupeStatuses) in /_/src/DurableTask.Netherite/OrchestrationService/NetheriteOrchestrationService.cs:line 594\r\n   at DurableTask.Core.TaskHubClient.InternalCreateOrchestrationInstanceWithRaisedEventAsync(String orchestrationName, String orchestrationVersion, String orchestrationInstanceId, Object orchestrationInput, IDictionary`2 orchestrationTags, OrchestrationStatus[] dedupeStatuses, String eventName, Object eventData, Nullable`1 startAt) in /_/src/DurableTask.Core/TaskHubClient.cs:line 614\r\n   at Microsoft.Azure.WebJobs.Extensions.DurableTask.DurableClient.Microsoft.Azure.WebJobs.Extensions.DurableTask.IDurableOrchestrationClient.StartNewAsync[T](String orchestratorFunctionName, String instanceId, T input) in D:\\a\\_work\\1\\s\\src\\WebJobs.Extensions.DurableTask\\ContextImplementations\\DurableClient.cs:line 210\r\n   at Microsoft.Azure.WebJobs.Extensions.DurableTask.HttpApiHandler.HandleStartOrchestratorRequestAsync(HttpRequestMessage request, String functionName, String instanceId) in D:\\a\\_work\\1\\s\\src\\WebJobs.Extensions.DurableTask\\HttpApiHandler.cs:line 875\r\n   at Microsoft.Azure.WebJobs.Extensions.DurableTask.HttpApiHandler.HandleRequestAsync(HttpRequestMessage request) in D:\\a\\_work\\1\\s\\src\\WebJobs.Extensions.DurableTask\\HttpApiHandler.cs:line 306"}
    at DurableOrchestrationClient.createGenericError (C:\home\site\wwwroot\node_modules\durable-functions\lib\src\durableorchestrationclient.js:612:16)
    at DurableOrchestrationClient.<anonymous> (C:\home\site\wwwroot\node_modules\durable-functions\lib\src\durableorchestrationclient.js:404:44)
    at Generator.next (<anonymous>)
    at fulfilled (C:\home\site\wwwroot\node_modules\durable-functions\lib\src\durableorchestrationclient.js:5:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

[sebastianburckhardt]

Unfortunately, the client request timeouts can have many reasons. It basically means the client did not receive a response from the partition in time; but it contains no information about why. Usually the next step is to take a look at the logs for the target partition.

Is this running in a consumption or premium plan? If so, I can take a look at the trace in our internal telemetry if you tell me the appname.

[thegrekle]

app name: iothubprod, it is running in a consumption plan

Thank you