Attribute Rollback
A bad import wrote the wrong title, department or mail. Pick that import, see the values history can put back, isolate the source rows, and restore them. The export carries the restored values.
Undo one import
Pick the bad import
Choose the source connector and Identity Mesh lists its recent imports that changed mesh attributes, newest first, with the objects and attributes each one touched. Times are shown in your local zone and in UTC. Imports whose run record has already been purged are still listed, grouped into bursts, for as long as the attribute history holds them. That history is 7 days.
Preview before anything is written
Each attribute on each object is Restore, Unchanged, Conflict, or Not restorable. A conflict is a value someone else wrote after the bad change; it is restored only if you ask. Sensitive values, values history truncated, and multi-valued values that history cannot split are not restorable. A point in time older than 7 days is warned: those rows may already be gone.
Isolate, restore, export
Isolate the source rows so the next import cannot write the bad values straight back. Apply writes the Restore values, and Conflicts only when you include them. Open source rows are skipped. Each restored object is queued for export to every connector, and Composer runs again. Attribute-change workflows do not fire for the rollback unless you ask.
A record, not a button you cannot undo
- A rollback is a tracked record: draft, submit, approve, reject, apply, release, undo, or cancel. The preview counts are saved with the draft.
- At or above the approval threshold (50 objects unless you change it), a different administrator approves the rollback before it can be applied.
- Undo puts the values the rollback replaced back, and leaves edits made after the rollback unless you force it.
- Release uses the rollback's own object list, so it still works after attribute history is purged, and reports restored values the source has changed again.
- Download an evidence CSV of what was replaced and what was restored. On the person's page: the rollbacks that touched them, the attribute history, and restore one earlier value.
- The object audit records AttributeRollback, AttributeRollbackUndo and AttributeRestore. Those kinds are in the SIEM catalogue.
Import safety net
While an import runs, the engine counts how many mesh objects that run has changed. Past the limit it opens a quarantine and the export engine holds exports of those objects until an administrator accepts the changes or rolls the run back. Objects the same run changes later join the quarantine. Exports already sent before the net tripped are not recalled; the rollback puts those right.
On by default. The limit is 500 objects, or 20 percent of the connector's objects when that number is lower. The percentage applies once the connector has at least 100 objects. Turn the net off, or set either limit for one connector.