Problem

So happened when the whole target text with tags from source added as one track change and target also has terms it may cause tag sequence error.

If general internal tag comes first and terms are after it and all of it is one and only <ins> track change in segment - it may play a trick of disposition of tags and cause an error.

Tricky part is that to produce such a segment you'll need to use package re-import.

Solution

Fix tag ordering on term tagging.

Test

Nowhere easy to test...

You'll need xlf file with 1 segment to translate.

Segment should have some tag in the beginning - so I recommend to start it with int and make use of content protection.

Also segment needs to have a couple of terms.

So it should have structure like:

Plain: 1 segment with term
With markup: <cp n="1" /> <term id="1">segment</term> with <term id="2">term</term>

Then you'll need term collection with those 2 terms both for source and target languages.

So you import the file to create a task, export translator package, update file in it as if you would work on it in some other up and provide translation, import translator package back into task.

This should produce updated task for you with segment in target as one big track change.

In master it should fail, but in feature branch - not.

Error will be smth like:

Tag "<ins class="trackchanges ownttip" data-usertrackingid="14733" data-usercssnr="usernr1" data-workflowstep="firsttranslation1" data-timestamp="2026-08-31T09:50:26+02:00">" starts at 0, but previous tag ended at 16.