RetryPolicy
Attributes
- Source:
- Retry.scala
- Graph
- Supertypes
- Self type
- RetryPolicy.type
Members list
Value members
Concrete methods
Decomposes a retry policy into components that are typically configured individually.
Decomposes a retry policy into components that are typically configured individually.
Attributes
- backoff
a function of attempts to an optional FiniteDuration. Return None to stop retrying, or some duration after which the request will be retried. See
exponentialBackofffor a useful implementation.- retriable
determines whether the request is retriable from the request and either the throwable or response that was returned. Defaults to
defaultRetriable.- Source:
- Retry.scala
Returns true if (the request method is idempotent or request contains Idempotency-Key header)
and the result is either a throwable or has one of the RetriableStatuses.
Returns true if (the request method is idempotent or request contains Idempotency-Key header)
and the result is either a throwable or has one of the RetriableStatuses.
Caution: if the request body is effectful, the effects will be run twice. The most common symptom of this will be resubmitting an idempotent request.
Attributes
- Source:
- Retry.scala
Attributes
- Source:
- Retry.scala
Returns true if parameter is a Left or if the response contains a retriable status(as per HTTP spec)
Returns true if parameter is a Left or if the response contains a retriable status(as per HTTP spec)
Attributes
- Source:
- Retry.scala
Like isErrorOrRetriableStatus but allows the caller to specify which statuses are considered retriable
Like isErrorOrRetriableStatus but allows the caller to specify which statuses are considered retriable
Attributes
- Source:
- Retry.scala
Like defaultRetriable, but returns true even if the request method is not idempotent. This is useful if failed requests are assumed to have not reached their destination, which is a dangerous assumption. Use at your own risk.
Like defaultRetriable, but returns true even if the request method is not idempotent. This is useful if failed requests are assumed to have not reached their destination, which is a dangerous assumption. Use at your own risk.
Caution: if the request body is effectful, the effects will be run twice. The most common symptom of this will be resubmitting an empty request body.
Attributes
- Source:
- Retry.scala
Concrete fields
Statuses that are retriable, per HTTP spec