# GROUP_NOT_FOUND

Canonical page: https://docs.ovok.com/errors/group-not-found

**HTTP 422.** Problem type: [`https://docs.ovok.com/errors/group-not-found`](https://docs.ovok.com/errors/group-not-found).

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

No `translations` group has the slug you named, and the call did not meet the conditions for creating one. A call creates a group only in the default locale and with a `title`. Nothing was written.

## Troubleshooting [#troubleshooting]

1. Check the `slug`. List the groups with `list_cms_documents` on `translations`, since a typo reads as a new group.
2. To create the group, call `set_cms_translations` with the default locale from `get_cms_schema` and a `title`. Add other locales afterwards, one call each.
3. If the group existed before, someone deleted it, and its text in every locale went with it. Create it again in the default locale, then write the other locales again.

## Retry safely [#retry-safely]

Retry with the right `slug`, or with the default locale and a `title`. An unchanged call returns the same error. Nothing was written.

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