EVENTS UNAVAILABLE
Troubleshoot events unavailable responses from the Ovok API.
HTTP 503. Stable Problem Details type: https://docs.ovok.com/errors/events-unavailable.
What this means
Ovok could not read the project's request-event service in time or the service is temporarily unavailable. Clients should branch on type and status, not on human-readable detail text.
Troubleshooting
Inspect Retry-After, retain the request trace ID, and check if failures affect all event-history reads. Verify write state before repeating related operations. Compare the request with the relevant endpoint's documentation and confirm the authenticated project and environment. Record the request path and traceId before escalating; the identifier lets an administrator find server-side context without sharing credentials or patient data.
Retry safely
For a 5xx response, wait for Retry-After when present and retry with bounded backoff. Before replaying a write, read the affected resource or operation state to avoid duplicate effects. Follow endpoint-specific idempotency and concurrency guidance. Do not retry in a tight loop or use a broader permission or project setting to bypass the check.
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 sensitive patient data from the report. The Error responses guide explains the response fields, while the machine-code registry lists every endpoint-specific type audited for this release.
Last updated on