AI Gateway now supports automatic retries at the gateway level. When an upstream provider returns an error, your gateway retries the request based on the retry policy you configure, without requiring any client-side changes.
You can configure the retry count (up to 5 attempts), the delay between retries (from 100ms to 5 seconds), and the backoff strategy (Constant, Linear, or Exponential). These defaults apply to all requests through the gateway, and per-request headers can override them.
This is particularly useful when you do not control the client making the request and cannot implement retry logic on the caller side. For more complex failover scenarios — such as failing across different providers — use Dynamic Routing.
For more information, refer to Manage gateways.
Source: Cloudflare
Latest Posts
- (Updated) Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft [MC1251200]
![(Updated) Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft [MC1251200] 2 pexels felixmittermeier 957090](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- AI Gateway – Automatically retry on upstream provider failures on AI Gateway

- Amazon CloudWatch launches OTel Container Insights for Amazon EKS (Preview)

- Amazon ElastiCache Serverless now supports IPv6 and dual stack connectivity


![(Updated) Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft [MC1251200] 2 pexels felixmittermeier 957090](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-felixmittermeier-957090-150x150.webp)


