Repair and rollback
Two ways to deal with a migration that did not land properly: fix the pages forward, or put them back. Both are driven by the log you downloaded at the time.
Every one of these writes a new page version with its own version message, so a repair is itself visible in page history and undoable from there.
Repair tools exist only for draw.io diagrams. A failed macro from any other app is handled by re-running, rolling back, or sending us a debug bundle.
#In this section
Before you repair anythingThe safety rules every repair tool shares, and the one habit that prevents most regret.Repair diagram versionsMigrated draw.io diagrams that display their oldest content instead of their newest.Repair diagram tabsMulti-tab diagram files embedded several times on one page, where every resulting reference shows the first tab instead of the tab the author chose. It also replaces machRepair diagram layoutNot a bug fix, a bulk settings change. Switches migrated draw.io diagrams between the classic draw.io layout and Capable's Auto layout. Migrations run before the layoutRolling back a migrationUndoes a migration by restoring every page the run changed.
#Related
Fix forward, or put it back. Both need the log.
