translationStatus tells you whether a locale is fully approved or partially machine-filled
Because translation happens lazily, the honest signal for consumers is the translationStatus field on the resolved pack: translated or fallback. Reading it tells you how much of the report a client can trust as reviewed text.
What fallback means#
A fallback pack is not broken or English-only — every key has a string. It means at least one key was filled by machine translation without an approved memory entry, so the pack mixes approved and provisional text. English always resolves as translated, and locales with complete prebuilt packs never downgrade; only the lazy per-key path can produce fallback.
Working with it#
There is no admin screen that lists locale status — resolution happens inside report generation. Your integration can call the localization endpoints for your tenant to inspect glossary terms (GET /v1/glossary-terms) that shape translation, and should treat fallback as a review queue: once memory holds approved text for the outstanding keys, subsequent generations flip the status to translated automatically (see How translation resolves).
Expected result#
Reports always render in the requested locale, with a truthful status attached — never a silent half-translation labeled as complete.