Downloading the run log
This is the most important habit on the whole branch: download the log before you navigate anywhere. Results are held in the page you are looking at, not on a server, and pressing Back to selection or Start migration wipes them.
The log is also the key that unlocks repair and rollback. Without it, three of the four tools have nothing to work from.
#What is in it
The run summary: every migrator used with its support level, the exact search, the options you chose, the behaviour version and its release date, and whether the run was verification only.
Every page result, with the page title, space and a link to it.
Permission warnings and any run-level error.
Run metadata: timings and counts.
It contains no page bodies, so it is safe to attach to a ticket.
#When you can download it
Situation | Available? |
|---|---|
Mid-run, as soon as there are results | Yes |
After a completed run | Yes |
After a verification pass | Yes |
While reading a previously saved log | No, you already have it |
#Opening a saved log
The "Open log" button in the header re-opens a downloaded log in exactly the same results screens, badged "Saved run, read only". Every drill-down works. That is how you review a migration somebody else ran, or one from last month.
There is no server-side copy. If the tab is closed without downloading, the detail of that run is gone. The pages are still migrated and page history still holds the originals, but the report and the repair path are lost.
#A few things that catch people out
Download it before pressing Back to selection or Start migration. Both wipe the screen.
Rollback needs that exact run's log and refuses to run against a different site.
Repair tools match on the wording used in the log, so a log from a much older app version may find no candidates.
#Related
Download it first. Always.
