Run only what changed

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.

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.

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.

Every run asks you to confirm it first, in two steps. The first is the confirmation: what will run, what it runs on (the paragraphs you’re looking at, the whole document, or all languages), roughly how long it takes, and what it costs against your balance, as in “1,926 of your 5,500 credits”. When the run uses Pro, a line under the price gives the same run on Standard. Translate, Translate + Proofread and workflow runs open on the whole document when your balance covers it, and otherwise on the paragraphs on your screen (Paragraphs 51–100).

If your balance won’t cover the run, the dialog says so and shows the smallest credit pack and the smallest plan that cover it, side by side, each with its price. Under them, Use Standard instead switches a Pro run to Standard when that fits your balance, and Translate what fits (Run what fits for a run that doesn’t translate) runs the part your credits cover now; these runs, like the dialog itself, are on the paid plans. That part starts at the top of the document, or at the first untranslated block when the run translates, so running it again later picks up where it stopped.

The second step is behind Customize, and you rarely need it. It opens on the model tier, glossary and style guide, and guidance for this one run. The rest sits under Advanced: the Context switch, Ignore Previous Versions (when you regenerate) and Ignore Reviewer Comments, translation memory, and whether several agents work in parallel. A dot beside Advanced means something in it is off its usual setting. All of it already follows the document’s own settings, so pressing Run without opening Customize does the right thing.