apiwrappers | Build API clients that work both with regular and async code | REST library

Based on the provided code I can see the following resilient strategy:

100 seconds global timeout

5 retries (= 5+1 attempts)

Exponential back-off logic

10 seconds local timeout

If I understand your problem correctly then you are looking for a solution to increase the global timeout.

The simplest solution (1) is to increase the HttpClient instance's Timeout property from the default 100 to the desired value. If this timeout is exceeded then the instance will throw an OperationCanceledException and no further retry attempt can be established.

If the HttpClient instance is shared / reused amongst different components then you might need to change the global timeout per usage. You can overcome on this by introducing a new Timeout policy between the HttpClient's global Timeout and your Retry policy.

So, you could end up with the following setup:

200 seconds global timeout (by HttpClient

150 seconds overall / overarching timeout (by outer timeout policy)

5 retries (= 5+1 attempts)

Exponential back-off logic

10 seconds local timeout

In this particular case I would recommend to use Policy.WrapAsync (1) just like this: