Before you repair anything
Repair tools fix forward: they change migrated content in place rather than undoing anything. That makes them fast and it makes them worth a moment of care.
All four share the same shape and the same guards, so it is worth reading this once rather than four times.
#What they all have in common
They only look at pages you hand them. None of them sweeps the site. Pages come from a downloaded run log, or from a pasted or searched list of page ids.
They scan live pages first to confirm what is actually wrong before writing anything.
Bulk operations stay locked until you have fixed and checked a single page by hand. That gate is deliberate.
Every write is a new page version with its own version message, so repairs are visible in page history and are themselves undoable.
#Where they fall short
Repair tools exist only for draw.io diagrams. A failed macro from any other app has no fix-forward path beyond re-running, rolling back, or sending a debug bundle.
They run as you, with no admin key option and without the rate-limit retry the migration itself uses, so their reach can be narrower than the run that created the problem.
A repair rewrites the whole page, not just the macro, and the page body is normalised on the way through. That can incidentally tidy unrelated formatting.
Cancel is cooperative: it stops the queue between pages, so pages already in flight will still complete and write.
Fix one page, look at it, then release the batch. The product enforces this, and it is the right habit even where it does not.
#A few things that catch people out
Three of the four tools need the run log. Download it at the time; you cannot recreate it later.
Two tools also accept pasted page ids, which is how you reach pages the log cannot identify.
A tool reporting "0 to fix" is often correct. Check a page by hand before assuming the tool is broken.
#Related
Fix one page. Look at it. Then the rest.
