Skip to content

Stockertim Dictionary · Technology · Artificial intelligence

Rollback

Also called roll back, roll-back, rollbacks

In short

A rollback returns a system to its last known good version, such as the previous prompt, settings or workflow, when a change causes errors, so service recovers while the cause is found.

  • Beginner
  • Process
  • Checked

In detail

Changes to automations go wrong in ways testing did not catch: a reworded prompt that mishandles a common case, a new model that formats dates differently, a workflow edit that skips a step. A rollback undoes the change quickly by restoring the version that was working before. It separates two jobs that otherwise get confused under pressure: restoring service now and understanding the fault later.

Rollback is only quick if it was prepared. Every version of the prompt, the settings, the model choice and the workflow needs to be saved with a version number, so the previous one can be restored exactly rather than reconstructed from memory. Many teams change one thing at a time, so that when a rollback is needed it is clear what to roll back.

Rolling back the system does not roll back its effects. Emails already sent, records already changed and payments already made by the faulty version remain, and the period between the change and the rollback has to be reviewed separately. Changes to stored data, such as a renamed field, can also make the old version incompatible, which is why such changes are planned with a way back.

A rollback is a decision as well as a mechanism. The runbook usually sets the trigger, such as error rates above an agreed level after a release, and who may make the call, so nobody waits for permission while errors pile up.

Worked example

Lindenfield Recruitment updates the prompt that extracts candidate details from CVs to version 7.

  1. The next morning, live sampling finds dates of employment missing from 9 of 30 sampled outputs: 9 / 30 = 30%
  2. The duty owner follows the runbook and restores prompt version 6, saved with its settings.
  3. Outputs produced while version 7 was live are listed and rechecked.
  4. The fault is traced to a new instruction, fixed and retested before version 8 goes live.

Normal service returns within the hour, and the affected outputs are found and corrected rather than left in the records.

In practice

Teams version every prompt, setting and workflow, change one thing at a time, define in the runbook when to roll back and who decides, rehearse the rollback, and review whatever the faulty version did while it was live.

Watch out

  • Restoring the old version leaves the faulty version's actions in place; they need their own review.
  • Without saved versions, a rollback becomes a guess.

Learn it properly

Official sources

Facts last checked on 9 November 2026.

Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.

English