# RATE_LIMIT_EXCEEDED

Canonical page: https://docs.ovok.com/errors/rate-limit-exceeded

**HTTP 429.** Problem type: [`https://docs.ovok.com/errors/rate-limit-exceeded`](https://docs.ovok.com/errors/rate-limit-exceeded).

## What this means [#what-this-means]

The tenant sent Signals more requests in the current window than its limit allows, so Signals refused this one and ran nothing. The limit counts per Signals tenant, so every caller of that tenant shares it.

## Troubleshooting [#troubleshooting]

1. Wait for the delay in the `Retry-After` header. Earlier retries are refused again.
2. Spread your calls. Reduce concurrency, queue work that is not urgent and poll less often.
3. Send readings in batches where the route takes a batch, rather than one request each.
4. Remember that other apps and workers on the same project count toward the same limit.

## Retry safely [#retry-safely]

Do not retry before the delay ends. A refused request ran nothing, so repeating it later is safe. When several workers retry together, add a random pause to each so they do not collide again.

## If the problem persists [#if-the-problem-persists]

Share the HTTP status, problem `type`, request path, response timestamp and `traceId` with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
