# DEFAULT_LOCALE_FIRST

Canonical page: https://docs.ovok.com/errors/default-locale-first

**HTTP 422.** Problem type: [`https://docs.ovok.com/errors/default-locale-first`](https://docs.ovok.com/errors/default-locale-first).

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

`set_cms_translations` was called for a locale other than the CMS's default locale, with keys the group does not hold yet. New keys are created in the default locale first, so the tool wrote nothing. The error lists those keys in `keys`.

## Troubleshooting [#troubleshooting]

1. Call `set_cms_translations` with the default locale for the keys in `keys`. `get_cms_schema` shows the default locale.
2. Call it again for the other locale with the same keys. They now exist, so the call goes through.
3. Check each key in `keys` for a typo of an existing key. Fix the spelling instead of creating a new key. `get_cms_document` shows the keys the group holds.

## Retry safely [#retry-safely]

Retry after the default-locale call. An unchanged call returns the same error. Nothing was written, so there is nothing to clean up.

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