Migration results and re-runs
The results view groups everything by outcome, and each group is a tab rather than a static number. Clicking a count shows exactly which pages and diagrams are in it.
Most failures fall into a small number of categories, and most of them are re-runnable once the cause is cleared.
#When this applies
After any migration run, including dry runs.
Working out whether a failure needs action or was transient.
Producing evidence that a migration completed.
#How it works
Step | What happens |
|---|---|
Succeeded | Migrated and verified. Nothing further to do. |
Failed | Reported with a reason. Most are re-runnable. |
Skipped | Already migrated, or out of scope. |
Download log | A full log file for offline review or for sending to us. |
Re-run failures | Runs again over the failures only. |
#A few things that catch people out
A failure is not a data loss. The original diagram is untouched, so a failed item can always be retried.
Transient failures do happen on very large runs. Re-running is the correct first response.
If the same item fails twice with the same reason, that is worth sending to us with the log.
#Related
Nothing is deleted. Try a dry run.
