You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: product/ai-gateway/automatic-retries.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ You can change this behaviour by setting the optional `on_status_codes` param in
50
50
51
51
### Respecting provider's retry headers
52
52
53
-
Portkey can respect the provider's `Retry-After` and `Retry-After-ms` response headers when encountering rate limits. This enables more intelligent retry timing based on the provider's response headers rather than using the default exponential backoff strategy.
53
+
Portkey can respect the provider's `retry-after-ms`, `x-ms-retry-after-ms`and `retry-after`response headers when encountering rate limits. This enables more intelligent retry timing based on the provider's response headers rather than using the default exponential backoff strategy.
54
54
55
55
To enable this feature, add the `use_retry_after_headers` parameter to your retry config. By default this behaviour is disabled, and `use_retry_after_headers` is set to `false`.
0 commit comments