RATE_LIMIT_EXCEEDED
Signals rate limit reached: what the RATE_LIMIT_EXCEEDED error means and how to fix it.
HTTP 429. Problem type: https://docs.ovok.com/errors/rate-limit-exceeded.
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
- Wait for the delay in the
Retry-Afterheader. Earlier retries are refused again. - Spread your calls. Reduce concurrency, queue work that is not urgent and poll less often.
- Send readings in batches where the route takes a batch, rather than one request each.
- Remember that other apps and workers on the same project count toward the same limit.
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
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 explains the response fields, and the machine-code registry lists every endpoint-specific type.
Last updated on