UPSTREAM_TIMEOUT
Recover from an upstream service that did not answer before Ovok's deadline.
HTTP 504. Problem type: https://docs.ovok.com/errors/upstream-timeout.
What this means
A required upstream service did not answer before the request deadline. The timeout does not by itself tell you whether the upstream completed a state-changing action.
Troubleshooting
Check the affected endpoint and integration, and note whether the issue repeats or affects multiple operations. For a write or external action, verify the current resource or documented operation status before replaying the request. If the call has a documented asynchronous status check, use that instead of starting parallel copies of the same work.
Retry safely
Retry only a safe operation after a delay, using a bounded backoff. Confirm the result before repeating a write, and avoid overlapping retries. If timeouts persist, 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