# UNEXPECTED_CMS_ANSWER

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

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

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

`set_cms_translations` read the translations group from the CMS and could not understand its shape, so it wrote nothing. The tool needs the group's `id` and `updatedAt`, and every row of `strings` with its own `id`.

## Troubleshooting [#troubleshooting]

1. Read the group with `get_cms_document` on `translations`, with `locale` set to `all`. Look for a missing `id` or `updatedAt`, or a `strings` row without an `id`.
2. Fix the group in the console, or recreate it, then call the tool again. Without a row's `id`, its text in the other locales would be lost, so the tool refuses to write.

## Retry safely [#retry-safely]

Retry after the group is fixed. An unchanged call returns the same error if the shape is the cause. 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.
