File Issues

What lands on File Issues

A file is listed when a run met a problem with it. For example, a file whose type an admin policy blocks from upload — such as .exe files refused by Nextcloud's File access control — cannot be migrated, and is listed here with the reason. A file whose metadata could not be carried over is listed too, unless Migrate Files With Metadata Warnings is on.

The table's columns are File Name — the file's own name — Path, the folder it is in, File Modified, when the file was last changed in its source, Error Message — why SMART Migration could not handle the file, in its own words — Issue Created, when the issue was recorded, Run Title, the run that recorded the issue, and Group, the run's group, with Pin at the far right. A long message is cut short on its row; rest the pointer on it, as on the file name, for the issue's card, which shows it whole, line for line. A web address's encoding is undone for reading — Shared%20Documents shows as Shared Documents — and the filters find either spelling. When every file is on one tenant, the paths leave out its address and start at ../sites/ — a OneDrive on the same tenant at ../personal/ — as the sources do on the Jobs and Run History tabs. When the window is too narrow for every column, the table scrolls sideways: the row menu, the tick boxes and File Name stay in place at the start, and the Pin column at the end, so you always know which file a row is. While the table scrolls sideways, the lines after File Name and before Pin turn blue: the columns between them are the ones that scroll.

Rest the pointer on a file name to see the issue's summary card: the file name and its whole path, the error message, the run and its group, and the source. Click the file name or the message to pin the card: it stays, and offers Details, Go to Job, Go to Run History, Pin and Delete …, and the group on it filters the table to that group. Rest the pointer on a run's title for the run's own summary card, as Run History shows it but without the run's and job's ids at its foot; click the title to pin it, with Details — the run's details and session log — Open run on Run History tab, Goto Job and Copy link, and its note. Details in the row menu, or a double-click, opens the issue with every field: the file name, the error message, when the file was last modified, where it came from, the run, its Run History ID and Job ID, and when it was recorded. Its Copy link copies a web address that opens this issue's details straight away — for a handover, a mail or a ticket; anyone else with access to this app can open it.

Find the issues of a run

From Run History: a run with issues shows the issues mark and their number beside its Result; click it to open just that run's files here. A frame above the table names the run — its title, when it started and when it finished — and marks it Latest run when no run of the job came after it; rest the pointer on it to see the run's card, and click it to pin the card. Select run beside it switches to another run of the same job that recorded issues, each listed with its number of them; runs without issues are left out, and the choice is not there when no other run has any. The choice stays when you go to another tab and come back; Show all issues brings the rest back.
By group: the filter under the Group title is shared with the Jobs and Run History tabs, so the issues of one migration wave are one click away.
By text: each text column has a filter box of its own under its title. The one under File Name matches the file's own name or its note; the one under Path the folder the file is in — Shared Documents also finds Shared%20Documents — the one under Error Message the message, and the one under Run Title the title of the run the issue came from. Boxes filled in together must all match. A tree row's Show only this location fills in the Path box.
In the tree: the issues are filed under their run's group, then under the SharePoint site and library — or the file share — their own file is in, whatever the run read: the issues of a whole-site job or a File List CSV job fall into each library they came from. Tick the box on a group's, a site's or a library's row to select every issue under it.

Right-click a file name or a path for Copy URL — Copy UNC path for a file on a file share — which copies the file's whole address, or its folder's from the Path cell, and Open SharePoint location, which opens the file's folder in SharePoint in a new browser tab. A browser cannot open a file share from a web page: paste the path into File Explorer instead.

From an issue's row menu, Go to Job and Go to Run History open the job and the run it belongs to. Go to Run History — and Open run on Run History tab on the run's card — shows the run among its job's runs: the Run History tab narrowed to that job, with the run ticked and marked as the current row. A frame above the table names the job; Show all runs brings every job's runs back.

Act on several issues at once

Tick the issues to act on: the Actions menu appears above the tick boxes, at the start of the column titles; its tooltip says how many are ticked. It offers Pin, Unpin and Delete …, which asks before it deletes. Hold Shift and click another row to tick every row in between.

Pin issues to the top

A pinned issue moves to the top of the table: it is listed apart, under a Pinned band above the tree or the list, and no longer in its run below — whatever the sort, with a line in orange down its start edge. They stay in view under the column titles while the rest scrolls under them, as long as they take at most three quarters of the table's height; more than that, and they scroll with the rest. The Pin column at the far right shows a solid pin on a pinned row and an outline on the rest; click it to pin or unpin that row alone. An unpinned row leaves the band and the table stays where it is; the toast that says so takes you to the row.

The issue's details dialog has Pin and Unpin too.
Pinning changes nothing else: the issue keeps its place in the tree, its status and everything SMART Migration reads.
Pins are your own: each administrator pins for themselves, and no one else sees your pins.

My note on an issue

My note is a few lines kept with one file issue: what was decided about that file, who asked about it, whether it can be ignored. Write it in the issue's details dialog, or on its pinned summary card in My note about this issue; it is saved when the dialog or the card closes. It is your own: other administrators do not see it, and each can write their own. SMART Migration never reads it. The text filter under the File Name column reads notes too, and an issue with a note shows a small orange triangle in the top-right corner of its title.

For how to use notes with groups, tags and pins, see Organise the jobs of a project

Duplicates: the same file reported twice

The same Duplicates filter is on the Jobs and Run History tabs too, for jobs and runs — see Change many jobs at once

Duplicates, in the tab bar beside the count of issues shown, shows only the issues that share something with another, ignoring case, each set together. Pick one or both:

Same Filename: the issues whose files have the same name — the File Name column — in any folder.
Same path: the issues whose files are in the same folder — the Path column — so a folder with many problems stands out: a folder the service account cannot read, or one a policy blocks.
Both: the same file — its name in the same folder — reported more than once. Running a job again reports a file that still has the same problem again; Select duplicates ticks every duplicate except the first of each set, ready to delete.

The text filters work with Duplicates: an issue shows when its text matches and it has a twin among the issues the Group filter and the run you opened let through, even when the twin's text does not match. Select duplicates ticks only among the rows shown, and leaves the first of each set; it is greyed out while the rows shown hold no second of any set.

Fix the cause and run the job again

Read what happened
Open the issue, and if needed the run's log on the Log tab of its run details.
Fix the cause at the source
Rename the file, move it, change the policy that blocks it, or correct its metadata.
Run the job again
With the default rule, Add New Overwrite Existing By Newer, the next run adds what is missing and leaves what already arrived.
Check what is left
The next run reports the files that still have a problem. Delete the issues that are dealt with.

Issues are deleted with their run when a Run History row is deleted for good; deleting an issue on its own removes only the issue row. The rules for running a job again are in Rules for adding and overwriting files

See also