DEFAULT_LOCALE_FIRST
Default locale needed first: what the DEFAULT_LOCALE_FIRST error means and how to fix it.
HTTP 422. Problem type: https://docs.ovok.com/errors/default-locale-first.
What this means
set_cms_translations was called for a locale other than the CMS's default locale, with keys the group does not hold yet. New keys are created in the default locale first, so the tool wrote nothing. The error lists those keys in keys.
Troubleshooting
- Call
set_cms_translationswith the default locale for the keys inkeys.get_cms_schemashows the default locale. - Call it again for the other locale with the same keys. They now exist, so the call goes through.
- Check each key in
keysfor a typo of an existing key. Fix the spelling instead of creating a new key.get_cms_documentshows the keys the group holds.
Retry safely
Retry after the default-locale call. An unchanged call returns the same error. Nothing was written, so there is nothing to clean up.
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