Rollback and its limits

The app calls rollback_change with a receipt ID and a new idempotency key; the tool restores what it changed, from a revision or a snapshot taken before the write. If the target changed after that write, the rollback needs approval like any other change. A receipt can be rolled back once.

No rollback

• Writes that only clear regenerated data: caches, rewrite rules.
• Permanent deletes, including plugin, theme and media deletion.
• Running an arbitrary ability through run_ability.
• Theme mods and custom CSS once another theme is active.
• WordPress updates (update_core), running a cron event now (run_cron_event), password reset emails (send_password_reset) and delete_all_transients.

Plugin and theme updates roll back their files only: the previous version is reinstalled, and what the new version changed in the database stays. The Tools reference lists each tool’s rollback.