# CMS_UNAVAILABLE

Canonical page: https://docs.ovok.com/errors/cms-unavailable

**HTTP 502.** Problem type: [`https://docs.ovok.com/errors/cms-unavailable`](https://docs.ovok.com/errors/cms-unavailable).

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

The CMS did not answer, answered with an error, or sent a reply Ovok could not read, so Ovok could not serve the content request. The status says which: 502 for a failed or unreadable reply, 504 when the CMS took too long, and 503 with `retryAfterSec` when it asked to be called later. `detail` carries no cause on these statuses.

## Troubleshooting [#troubleshooting]

1. Wait for the `Retry-After` header or `retryAfterSec`, or a few seconds if neither is present, then repeat the request. The CMS is usually back quickly.
2. Check whether other CMS requests fail too. If they do, the CMS itself is down or restarting, so wait for it to recover instead of repeating the call at once.
3. Read the document before you repeat a create, update or delete that timed out. The CMS may have applied the change before the reply was lost.

## Retry safely [#retry-safely]

Reads and public content requests are safe to retry, with a growing wait between attempts. A write that failed before the CMS was reached changed nothing. After a timeout, check the document first to avoid a duplicate or a repeated change.

## 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. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
