Currently, for network, server or rate limit errors, we simply raise the error.
It could be nice to propose a retry mechanism that can be configured finely on:
- Number of retries
- Type of errors
Ideally, we can set that config on the main client but also be able to override it through a dedicated parameter/argument on each method.
Quite similar to Speakeasy approach.
Currently, for network, server or rate limit errors, we simply raise the error.
It could be nice to propose a retry mechanism that can be configured finely on:
Ideally, we can set that config on the main client but also be able to override it through a dedicated parameter/argument on each method.
Quite similar to Speakeasy approach.