SERVER_ERROR
Handle an unmapped Ovok server error and gather details for diagnosis.
Fallback for an unmapped 5xx response. Problem type: https://docs.ovok.com/errors/server-error.
What this means
The request received a server-side error, but no more specific status-based problem page applies. Use the HTTP status, problem type, and response details to distinguish this from a specific upstream or service-availability error.
Troubleshooting
Record the response status, type, request path, timestamp, and traceId. If the request changed data, inspect the resource or operation status before replaying it. Check whether the issue affects one route or multiple requests and whether a later request succeeds; this helps an administrator locate a transient or recurring failure.
Retry safely
Retry only when the operation is safe to repeat, using a bounded delay between attempts. Avoid rapid retry loops and verify the result before replaying writes. If the error persists, stop retrying until the issue is understood.
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