From 6b35ee6dd568c092cd213926fcfe11546ceb47d9 Mon Sep 17 00:00:00 2001 From: Lina Lam Date: Mon, 13 May 2024 15:08:45 -0700 Subject: [PATCH] put exponential backoff as accordian --- docs/features/advanced-usage/retries.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/features/advanced-usage/retries.mdx b/docs/features/advanced-usage/retries.mdx index b4fa319308..4217d40bdb 100644 --- a/docs/features/advanced-usage/retries.mdx +++ b/docs/features/advanced-usage/retries.mdx @@ -11,9 +11,9 @@ Retrying requests is a common best practice when dealing with overloaded servers For more information on error codes, see the [OpenAI API error codes documentation](https://platform.openai.com/docs/guides/error-codes/api-errors). -### Exponential Backoff - -To effectively deal with retries, we use a strategy called **exponential backoff**. Exponential backoff involves increasing the wait time between retries exponentially, which helps to spread out the request load and gives the server a chance to recover. This is done by multiplying the wait time by a factor (default is 2) for each subsequent retry. + + To effectively deal with retries, we use a strategy called **exponential backoff**. Exponential backoff involves increasing the wait time between retries exponentially, which helps to spread out the request load and gives the server a chance to recover. This is done by multiplying the wait time by a factor (default is 2) for each subsequent retry. + ### Why Retries - Overcoming rate limits and server overload.