Conflicts and content history

This guide applies to the branch selected in Current branch. Keys, values, languages, tags and file mappings are independent between branches. See branch navigation and branch permissions.

Every current workspace member, including Viewer, can read a key’s content history. Editing requires Owner, Admin or Editor and active parents/key/language. History itself cannot be edited.

Resolve a concurrent edit

Each key definition has a metadata version; each language value has its own version. Two users can save different language cells independently. Saving the same cell from an old version returns 409. Clearing a stored value increments its version instead of resetting it. Translation edits do not advance the separate project settings version.

1. Keep your text in the edited cell after a failed save.
2. Read the displayed error and Current saved value (or Current key definition).
3. Compare both versions and revise the draft if needed.
4. Choose Keep draft with current version only after reviewing the current content.
5. Select Save or Save key to submit explicitly again.

Nothing is merged or overwritten automatically. Another concurrent change can still cause a new conflict. Network/service errors keep your draft but do not claim success; retry only after connectivity returns. Cancel, Escape and switching away from a changed editor ask before discarding. Reloading or leaving with an unsaved editor warns before the draft is lost.

Inspect one translation

1. Hover a language cell or focus its controls. On touch screens the history control stays visible.
2. Choose View translation history on the right of the cell. Missing translations also have history.
3. Read the key, language and branch in Translation history. The popup lists ten recorded language events per page, newest first, with the actor, branch and your browser’s time zone.
4. Use Previous, Next or Refresh. Closing and reopening also loads current history.
5. Press Escape or Close to return focus to the control. An open translation draft is preserved.

Desktop uses an anchored popup; narrow screens use a dialog. Only one opens at a time. Hover shows a tooltip without loading history. Key renames, descriptions and shared ICU contract changes remain in the general key history below. Inactive languages and archived content retain their readable history for current members.

Show differences starts off. Enable it to compare each recorded text change’s own Before and After, not two adjacent events. Insertions are underlined and removals are struck through; line breaks, whitespace and ICU templates are kept. Large changes show full text with an explanation instead of an expensive difference calculation.

Review approvals and revocations are historical actions. They do not prove that the current value is still approved and have no invented text snapshot. A generic saved change is not labelled as coming from a particular integration unless its record proves it. There is no restore or draft-fill action in this popup.

Loading, no recorded changes and load failure are separate states. Retry reloads a failed request; access loss requires checking the selected scope and current membership. Changing scope never substitutes another cell’s cached history.

Inspect complete key history

1. Select the key name in Translations to open the inline details above the table.
2. Select History.
3. Read the actor, timestamp, language (when applicable), operation and Before/After content.
4. Use Previous and Next to move through older changes. Choose Close details to return to editing cells.

History is newest first. Creating, renaming, changing the format/parameters, saving/clearing a value and archiving/restoring a key produce records. Unchanged saves do not create a fabricated content revision. The actor is the account that performed the operation; the displayed email reflects that account’s current identity information.

Content, history and the security audit record commit together. Failed validation and rolled-back transactions do not leave successful content changes. Archived keys retain history. Losing workspace membership removes access immediately on subsequent requests.

There is no one-click history restore or permanent key deletion. To reuse earlier content, copy the relevant text into a normal editor and save it under current permissions and validation.

Branch provenance

Forks inherit prior events without fabricating edits. History shows each event’s original actor and branch. Source events after a fork appear in another branch only when a merge connects the histories. Shared history describes origin; separate merge-result events describe the target’s actual changes. Shared ancestry survives deletion of its original branch.

Translation assistance

Applying assistance proposals records the approving user and provider/model provenance in content history. Generating or editing a proposal alone does not change translation history. Selected Apply is atomic and version checked; see suggestion review.