UNEXPECTED_CMS_ANSWER

Unexpected CMS answer: what the UNEXPECTED_CMS_ANSWER error means and how to fix it.

HTTP 502. Problem type: https://docs.ovok.com/errors/unexpected-cms-answer.

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

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

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 explains the response fields, and the machine-code registry lists every endpoint-specific type.

Last updated on

On this page