Translation states, statuses and origins

States

Every segment has one state per target language. The dashboard’s matrix, GET /status and GET /units/{external_key}/status show them.

State	Meaning	Refclient symbol
ok	Approved, and the source hasn’t changed since.	✓
stale	The source text changed after the translation was made.	stale
review	Translated and delivered (or about to be), waiting for an editor.	review
missing	No translation, or the last one was rejected or discarded.	·
attention	Translated, but held back by QA errors; decided in the review queue.	!

The rules apply in this order: missing, then stale, then attention, then review, then ok. So a translation in review whose source changed counts as stale.

Stale is computed, not stored. A translation is stale while the fingerprint it was made from differs from the segment’s current fingerprint. If an editor reverts the source text, the translation is current again.

A segment “needs work” (segments_needing_work) if it isn’t ok in at least one language.

Statuses

The dashboard shows the status of each translation:

Status	State	Meaning
Machine translated	review	Ready in GET /results, not yet acknowledged.
Pending review	review	Acknowledged: a draft or suggestion exists on the site.
Approved	ok	An editor approved it (or it was imported).
Rejected	missing	An editor rejected it.
Needs attention	attention	QA errors; not delivered.
Missing	missing	No translation.

What a job translates

State	Delta and translate jobs	With force
missing (incl. rejected)	Yes	Yes
stale	Yes	Yes
review	No	Yes
attention	No: decide in the review queue	Yes
ok	No	Yes

Origins

Origin	Where the text comes from
deepl	DeepL.
llm	The LLM.
tm_exact	An exact match in the translation memory; not billed.
human	An editor: corrected on approval, or fixed in the review queue.
imported	Sent by the connector as an existing translation.