What is in a run log
The run log is not just a report. It is the input to three of the four repair tools and to rollback, which is why downloading it is the habit worth forming.
It is also safe to share: it contains no page bodies.
#What it holds
The run summary: every migrator used with its support level, the exact search, the options chosen, the behaviour version and its release date, and whether the run was verification only.
Every page result, with page title, space and a link.
Permission warnings and any run-level error.
Run metadata: timings and counts.
#What it does not hold
Page bodies. For those you need a debug bundle, which is a separate, heavier export.
Attachment or diagram file contents.
Anything that would let a run be resumed. There is no server-side state to resume from.
#What it unlocks
Tool | Needs the log? |
|---|---|
Repair diagram versions | Yes, log only |
Repair diagram tabs | Log, or a pasted list of page ids |
Repair diagram layout | Log, or a pasted list of page ids |
Roll back pages | Yes, and it must be that exact run's log, from this site |
Open log (read the results again) | Yes |
Repair tools recognise candidates by matching the wording used in the log. A log produced by a much older app version may yield no candidates. Do not rely on cross-version log compatibility.
#A few things that catch people out
The log is available mid-run as well as at the end, so a run that has to be stopped still leaves a record.
It is per run. Keep one per wave rather than assuming a later log covers an earlier run.
Rollback refuses to run against a different site, which is a deliberate guard rather than a bug.
#Related
Download it. Three tools need it.
