Browse the help center

Run only what changed

Maintained by Mariia IvakhnenkoCo-founder

Change a few blocks of source text and you rarely want to re-translate the whole document. The Only what changed toggle limits a run to what actually changed, so the cost and the wait drop to match.

On this page

Where is the Only what changed toggle?

Transept keeps track of which blocks have changed since they were last translated. Every run confirmation puts that to use — Translate, Regenerate, Smart Proofread, Translate + Proofread and workflow runs alike. Only what changed sits under the scope picker, and it’s off by default: leave it off to run on everything, the way you always have.

It only appears when the document actually has changed content, and it tells you how much — "Source text changed in 12 blocks". On a document you uploaded and translated once, nothing has moved since, so there is nothing for the toggle to narrow and it stays out of your way. If you were expecting it and it isn’t there, that’s why.

What counts as updated

A block is marked updated when its source changes — because you edited the original text by hand, or because you re-imported the document and that block’s source came in different (the same mechanism that drives string-table updates over the API). A block that has never been translated into the current target language also counts as work to do.

What each run does with it

Translate and Regenerate limit the run to blocks whose source changed since their translation, plus any not yet translated — and the cost estimate drops to match, since you’re billed for a handful of blocks instead of the whole file.

Smart Proofread (and a workflow’s review step) reads the pages that changed — a proofread needs the surrounding text to judge consistency, so it covers a whole page, but only the pages you actually edited, not the whole document — and points you at the changed blocks on them so your attention goes where the edits were.

Workflows branch per step: translate and rewrite steps skip unchanged blocks, while review steps cover the pages that changed. The toggle also works with the all-languages fan-out, so a single source fix can be pushed across every language version in one run.

What else is in the run dialog?

Every run asks you to confirm it first, in two steps. The first is the confirmation: what will run, what it runs on (this page, the whole document, or all languages), roughly how long it takes, and what it costs. If your balance won’t cover the run, that’s where it says so — and offers to top up or move to a bigger plan without leaving the dialog.

The second step is behind Customize, and you rarely need it: the model tier, glossary and style guide, translation memory, guidance for this one run, and whether several agents work in parallel. All of it already follows the document’s own settings, so pressing Run without opening Customize does the right thing.

Explore the features

Still stuck? Ask Literess in the app, or write to [email protected].