A repetition is a segment whose source content is identical to another segment somewhere else in the same file (or, for a multi-file project, in another file joined to it). Instead of making you translate the same sentence over and over, wxrks fills every repetition in automatically from the first one it finds, top to bottom.
​
This matters beyond convenience: repetitions are counted separately in a project's Logfile and priced differently from new content, so understanding how they're detected and propagated affects both translation speed and project cost.

💡 Who is this for? This guide is for Vendors (translators and reviewers) working in the wxrks Editor, and for Account Admins and Project Managers who want to understand how repetition counts feed into a project's Logfile and cost.

Two segments are treated as repetitions of each other when their source content matches exactly - wxrks does not consider formatting tags when making this comparison, only the text to be translated. So a segment with bold text and a plain-text segment with the same words still count as repetitions of each other, even though their tags differ.
​
When a segment is a repetition, a small numbered badge appears at its lower right corner showing its position in the repetition chain - the first occurrence, then each one after it numbered in order.

Edit and confirm the first occurrence of a repeated segment, and every repetition below it can be filled in with the same translation automatically - propagation only ever flows top to bottom, never upward. If you instead edit a repetition that isn't the first one, only the repetitions positioned after the one you changed are affected; anything above it is left alone.
​
Editing and confirming a repetition's target now opens a Repetition Propagation Check dialog before anything is applied elsewhere, rather than propagating silently:

Three choices are offered:

Locked segments are never affected by any of these options, regardless of which one you choose. Choosing Propagate to all fills in every subsequent repetition immediately:

If you always answer the dialog the same way, you can stop it from opening:

From then on, confirming a repetition applies the option you clicked without opening the dialog. wxrks saves this to your user profile, so it still applies after you reload the page, open another task or sign in from another browser. It only changes how the Editor behaves for you, not for other people working on the project.

ℹ️ Note: Don't ask again only takes effect together with Propagate to unconfirmed only or Propagate to all. If you click Do not propagate, the dialog opens again the next time you confirm a repetition.

When a file needs a different choice, turn the dialog back on:

The dialog opens again the next time you confirm a repetition. The switch also works the other way: turning it off has the same effect as Don't ask again. The Editor then reuses the last option you chose in the dialog, or Propagate to unconfirmed only if you never chose one.

If the switch is grayed out with a lock icon, the editor preferences of your account, organizational unit (the team or department a project belongs to) or project lock this setting, and the tooltip says which one. The dialog then does not offer Don't ask again either. Ask your Project Manager or Account Admin if it needs to change.

Sometimes one occurrence of a repeated sentence needs a different translation. For example, "Open" may be a button label in one place and a ticket status in another. Mark that occurrence as a repetition exception: it keeps its own translation and stays out of propagation in both directions.

Marking a segment does not confirm it and does not change its translation. To undo it, click the badge again: the message Repetition exception removed appears and the segment goes back to receiving and sending propagation.

In the example below, segment 1 was translated as "Abrir" and confirmed. The translation reached segment 6, a regular repetition, but not segment 4, the exception.

Marking and removing exceptions requires the Repetition Exception permission. Account Admins have it by default; Project Managers and Vendors need it granted.

If you are an Account Admin, grant it to a Project Manager or Vendor:

If you are a Vendor translating or reviewing a task: once you have the permission, you mark and remove exceptions in the task's segments exactly as described above, and hovering over a badge shows Click to mark as repetition exception. Without it, you still see which repetitions are exceptions (struck-through icon) and your edits never propagate to them, but clicking the badge does nothing. If an occurrence in your task needs its own translation, ask your Project Manager to mark it or to grant you the permission.

Nobody can change the mark on a locked segment or in a task that is read-only, for example after it was delivered.

wxrks still pays attention to tags once it's decided two segments are repetitions of each other. Based on the previous version of this article and not independently re-verified against a live tag-mismatch scenario this session: if repeated segments carry the same number of tags but different content around them, wxrks respects each segment's own source tag placement rather than forcing identical tags everywhere. Conversely, if you save a repetition with a tag missing (for example, deleting a tag that should have carried over), the repetitions that come after it can pick up that same missing tag. If a translation looks like it's missing a tag it should have, check whether it's a repetition and whether an earlier occurrence in the chain was saved with that tag stripped out.

Repetition detection and propagation aren't limited to a single file. When two or more files are joined in the same project, segments with identical source content are linked as repetitions across those files too, and the same Repetition Propagation Check dialog above governs whether an edit carries over to the linked segments in the other file(s).
​
Cross-file repetitions are counted in the project's Logfile and included in cost calculation the same way same-file repetitions are, so consolidating similar content into fewer, larger files (or deliberately joining related files) can reduce the effective word count a project is priced on.