UPSTREAM_ERROR
Troubleshoot an unusable or unreachable upstream response through Ovok.
HTTP 502. Problem type: https://docs.ovok.com/errors/upstream-error.
What this means
An upstream service returned a response Ovok could not use or could not be reached. This points to communication between Ovok and a dependency, not necessarily to invalid request fields.
Troubleshooting
Check whether the failing operation depends on an external integration or other upstream service, and whether the endpoint documents a status or recovery procedure for it. Note whether the failure is intermittent or limited to one integration. Before repeating a write, inspect the resource or operation status because the upstream may have processed the request even if Ovok could not return a usable response.
Retry safely
For a safe operation, wait briefly and retry with a bounded backoff. Do not send repeated concurrent attempts. If the failure persists, stop retrying until the upstream service is checked.
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