# SYSTEM_TENANT_UNAVAILABLE

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

**HTTP 503.** Problem type: [`https://docs.ovok.com/errors/system-tenant-unavailable`](https://docs.ovok.com/errors/system-tenant-unavailable).

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

Ovok could not read its own platform records, such as system email templates and in-app notifications, because the CMS has no platform tenant to hold them. This points to the CMS deployment, not to your request. No platform record was changed.

## Troubleshooting [#troubleshooting]

1. Ask the operator of the environment to check that the CMS has been updated to a version that creates the platform tenant, and that its setup finished.
2. Ask the operator to confirm that the CMS holds a tenant marked as the platform tenant. Ovok looks it up on the first call and keeps it afterwards.
3. Wait for the fix before you rely on system emails or notifications in the environment. Your project's own content is not affected.

## Retry safely [#retry-safely]

Retrying helps only after the CMS is fixed. Until then every call that needs platform records returns the same error. These calls fail before they write, so repeating them is safe.

## 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.
