# CMS_REFUSED

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

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

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

The CMS rejected the translations group update that `set_cms_translations` sent, so nothing was written. The error lists the rejected rows in `errors`, each with the row's `id` and the CMS's own `message`.

## Troubleshooting [#troubleshooting]

1. Read `errors` and fix the value its `message` names, such as a key or text the CMS does not accept.
2. Look for a row with no key. An older row can lack one, and the CMS then refuses updates of the group until you give the row a key or delete it in the console.
3. Read the group with `get_cms_document` and compare it with what you send. Check `title` and `publish` too, as the CMS validates them with the strings.

## Retry safely [#retry-safely]

Retry after you fix what `errors` names. An unchanged call returns the same error. The CMS refused the whole update, so the group is as it was and needs no cleanup.

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