How to fix 100 seconds Grpc HTTP client timeout for Durable Task Client

Question

We are encountering an issue with GRPC HTTP timeouts being set to 100 seconds in our Azure Durable Function orchestrators. Our orchestrations often take longer than 100 seconds to complete, and we are having trouble changing the timeout duration to accommodate these longer operations.

From our understanding, it seems that the client is configured to time out after 100 seconds by default. Despite various attempts to adjust the timeout settings, we have not been successful in extending this duration.

Could you please provide guidance on how to configure the GRPC client to extend the HTTP timeout beyond 100 seconds for our durable function orchestrators? Any insights or solutions to address this timeout issue would be greatly appreciated.

Here is the line that is causing the problem. The call times out after 100 seconds.

var status = await client.WaitForInstanceCompletionAsync(instanceId, true, ctsOrchestrtor.Token);

Here is a picture of our error code:

Answer 1

To fix a 100-second gRPC HTTP client timeout for a Durable Task Client, you need to adjust the default timeout settings in the gRPC client configuration. This can typically be done by modifying the client settings in your code or configuration files. For instance, if you're using .NET, you can set the GrpcChannelOptions with a higher timeout value for HttpClient.Timeout. Ensure that you carefully manage these settings to avoid excessively long timeouts that might impact performance. For more details and professional assistance, visit https://cashfrenzy-777.com/