# Request rate is large. More Request Units may be needed, so no changes were made. Or retry after the Retry-After time.

- **ID:** `cloud/azure-cosmosdb-request-rate-too-large`
- **Domain:** cloud
- **Category:** resource_error
- **Error Code:** `429`
- **Verification:** ai_generated
- **Fix Rate:** 85%

## Root Cause

Application is sending requests to Azure Cosmos DB at a rate exceeding the provisioned throughput (RU/s), causing throttling.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Azure Cosmos DB SDK for .NET 3.31+ | active | — | — |
| Azure Cosmos DB SDK for Java 4.45+ | active | — | — |

## Workarounds

1. **Implement exponential backoff and retry in application code, respecting the Retry-After header from the Cosmos DB response.** (90% success)
   ```
   Implement exponential backoff and retry in application code, respecting the Retry-After header from the Cosmos DB response.
   ```
2. **Enable Cosmos DB autoscale throughput to automatically scale RU/s within a configured maximum.** (80% success)
   ```
   Enable Cosmos DB autoscale throughput to automatically scale RU/s within a configured maximum.
   ```

## Dead Ends

- **Increase RU/s to a very high value without monitoring** — May lead to cost overruns; also doesn't address bursty traffic patterns that could still trigger throttling. (50% fail)
- **Disable retry logic in the SDK** — SDK retries are designed to handle throttling gracefully; disabling them causes immediate failures. (50% fail)