Summary After our 28 September fix, five less common situations with the same symptom were found: a correction to an already confirmed segment stayed in its own workflow step, and the next step kept the earlier version. They existed before 21 September, independently of that release, and affect only projects with two or more linguistic steps. They were identified on 2 October. A release resolved them on 7 October.

The five situations

1. Saves of the same segment arriving almost at the same time, such as correcting and confirming in quick succession.
2. Glossary terms inserted into a confirmed segment.
3. Bulk actions: confirm or lock selected segments, confirm all, and fix tags across a file. Only some segments in an action were affected, depending on their state.
4. Repetitions updated together with the corrected segment.
5. Corrections made after the next step had started, which reached the next step but not the steps after it.
   

Root cause Propagation was implemented separately in each write path, so each had its own gaps:

• It depended on detecting a change of status. A confirmed segment changed again by any operation other than the normal editor flow never looked like a new confirmation.
• Glossary insertion, bulk actions, Fix All and repetitions each changed segments their own way, and several did not carry the new version forward.
• Propagation stopped at the next step.
• Saves were not ordered, so an outdated version could replace the current one.

Delivering a step did not repair these cases, because delivery only fills empty segments.

Timeline (2026)

• 2 Oct: Five situations were identified and published on this status page. Work starts on a single rule for every write path.
• 3–4 Oct: QA tests every operation against every segment state in three-step workflows, through the editor and the API, with several users on the same project.
• 5 Oct: the fix is validated in our test environment.
• 7 Oct: v2.14.0 is released to production.
  

Resolution

• Saves at almost the same time: each save is sent with its action (confirm, lock or draft) and the version it was based on, one at a time. The server rejects a save based on an outdated version.
• Glossary terms in a confirmed segment: every content change makes the segment a draft, including typing, glossary insertion, AI actions, tag fixes, undo and redo. Confirming it again carries the new version forward.
• Bulk actions: bulk confirm and lock, confirm all and Fix All carry their segments forward through the same service.
• Repetitions: repetition propagation uses the same service, and each repetition keeps its own tags.
• Corrections after the next step started: the latest confirmed version follows the whole chain of steps, passing over skipped steps and cancelled or expired tasks.

A segment the next step has already confirmed or locked is never overwritten. The segment history shows "Not applied: edited in this step" when the versions differ.

Also fixed in the same release

• A draft never leaves its step.
• XLIFF and XLSX imports, pre-translation and corrections in delivered tasks no longer overwrite segments the next step has already confirmed or locked.
• Step order and locked or reviewed segments are enforced on the server for the editor, the API and integrations.
• The translation memory is written only for segments confirmed by a person, not by pre-translation, automated confirmations, propagation between steps or the fill on delivery.