Schema reconciliation and processes
Apply schema changes responsibly when entries already exist.
WORKFLOWS
Review impact
When a definition change affects saved entries, the update flow previews its impact and can ask for decisions before it is saved.
Track background work
The Processes tab shows reconciliation and cleanup jobs. Schema deletion removes SQL data immediately and schedules known macro cleanup for affected pages.
Why reconciliation exists
Changing a schema does not silently rewrite every saved document. The update flow previews the impact of a definition change so an administrator can understand which entries need validation, repair or reindexing.
After save, background reconciliation processes work through affected entries. The Processes view is the place to monitor that work instead of assuming a large update is immediate.
Deletion and cleanup
Deleting a schema removes its SQL data immediately and schedules cleanup of known matching macros on affected pages. Review the impact carefully: deleting a schema is different from hiding a capture macro on one page.
Change safely
Review the impact before saving a definition that affects stored entries, then follow reconciliation progress in Processes.
Result
Apply schema changes responsibly when entries already exist.
Next step: Security, storage and limits