change-rollback
Installation
SKILL.md
Undoing a Change on a ServiceNow Instance
You overwrote a Business Rule script, or a widget's server script, or a Script Include, and the new version is wrong. Do not reconstruct the old code from memory. The instance already kept a copy of the record as it was before you touched it, in the sys_update_version table. Recovering it is a read, a copy, and a write — no guessing.
The rest of this guide is about getting that read right, and about the three or four cases where no read will save you.
Which mechanism undoes what
| Mechanism | Undoes | Driven from |
|---|---|---|
Version records (sys_update_version) |
One configuration record, field by field | This MCP (read the payload, write the field back), or the UI's Revert to this version |
| Back out an update set | Every change captured in one committed update set, including dictionary changes | ServiceNow UI only — there is no tool for it here |
Deleted Records (System Definition > Deleted Records) |
One deleted record plus its cascaded deletes, on audited tables | ServiceNow UI only |
| Nothing | Emails already sent, flows already run, data destroyed by a dropped column | — |
Pick the smallest one that covers the damage. Reverting one field of one record is safe and boring. Backing out an update set touches everything in it.