TOO_MANY_REQUESTS
Reduce request rate and retry after an Ovok rate-limit response.
HTTP 429. Problem type: https://docs.ovok.com/errors/too-many-requests.
What this means
The request rate is above the current limit. Sending more requests immediately can prolong the interruption, especially when multiple workers retry together.
Troubleshooting
Check for a Retry-After response header and review how quickly your application is sending requests, including parallel workers and automatic client retries. Reduce concurrency or queue non-urgent work so that retries do not create another burst. If 429 responses continue at a low request rate, ask an administrator to review the applicable endpoint or deployment limits.
Related endpoint guidance
Use these pages to check the route, project settings, and request requirements associated with this error:
Retry safely
Wait for Retry-After when present; otherwise back off before retrying. Use bounded attempts and retry only operations that are safe to repeat. For writes, verify the result or use the endpoint's documented deduplication mechanism before replaying a request.
If the problem persists
Share the HTTP status, problem type, request path, response timestamp, and traceId with your administrator or support contact. Do not include access tokens or sensitive patient data. The Error responses guide explains the response fields and field-level errors.
Last updated on