Backup and recovery
Create a snapshot before editing supported content and verify the result afterward.
What the backup tools cover
| Target | Create | Restore |
|---|---|---|
| Post or page | backup.post.create | backup.post.restore |
| Taxonomy term | backup.term.create | backup.term.restore |
| Elementor page data | elementor.page.backup | elementor.page.restore |
Post backups include content, metadata and term assignments. Use backup.list and backup.get_manifest to inspect available snapshots. These tools do not replace a full database and file backup.
Example workflow
The following calls show a sequence, not a single request. Replace IDs with values from your site and inspect the schemas first.
session.open({"name":"Update page copy","description":"Back up page 123, revise its copy and verify."})
backup.post.create({"post_id":123})
wp.posts.update({"id":123,"post_content":"Reviewed page content"})
wp.posts.get({"id":123})
session.close({})Restore
Open a named session and call the matching restore tool with the actual backup_id and required confirmation. Restore changes the target content; inspect the backup first and verify afterward. For Elementor content, use its page-specific backup and restore tools.
Retention and recovery limits
backup.purge_old deletes older backup records; backup.delete deletes a selected backup. Check their schemas and confirmation requirements before use. Session recovery depends on the recorded operations and available snapshots. File uploads and other unsupported operations may need a separate saved copy to recover.
AICOMBase sessions
In AICOMBase, inspect the work session and use recovery only where the service offers it for supported changes.
Reviewed for AICOM 3.23.1 · 22 October 2026. Your installed version and permissions determine available features.