GROUP_NOT_FOUND
Translations group not found: what the GROUP_NOT_FOUND error means and how to fix it.
HTTP 422. Problem type: https://docs.ovok.com/errors/group-not-found.
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
- Check the
slug. List the groups withlist_cms_documentsontranslations, since a typo reads as a new group. - To create the group, call
set_cms_translationswith the default locale fromget_cms_schemaand atitle. Add other locales afterwards, one call each. - 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 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
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