# REQUEST_TIMEOUT

Canonical page: https://docs.ovok.com/errors/request-timeout

**HTTP 408.** Problem type: [`https://docs.ovok.com/errors/request-timeout`](https://docs.ovok.com/errors/request-timeout).

## What this means [#what-this-means]

The request did not complete within the server's time limit. The timeout response alone may not establish whether a state-changing operation completed, so verify the outcome before replaying it.

## Troubleshooting [#troubleshooting]

Check whether the client or gateway also applied a shorter timeout, and note the affected route and request time. For a write, read the resource or check the documented operation status to see whether the change took effect. If the same read-only request repeatedly times out, reduce unnecessary response data where the endpoint supports it and report the `traceId`.

## Retry safely [#retry-safely]

Retry a read or other safe operation after a short delay, with a bounded retry policy. Before repeating a write, confirm its current result and follow any endpoint-specific deduplication guidance. Avoid simultaneous retries of the same timed-out operation.

## If the problem persists [#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](/errors) explains the response fields and field-level errors.