Every group of questions: Nextcloud FAQ
Run History
Section titled “Run History”These questions are explained in full in Run History
What is the difference between a job and its Run History?
The job is the plan you edit and run again; each Run History row is the fixed record of one time it ran. Plan and steer with jobs; follow, report and audit with runs.
Read more: Run History · Jobs and job modes
How do I clear up duplicate runs?
Pick Same Title, Same Source, Same Destination or Same Job in Duplicates, then Select duplicates: it ticks all but the first of each set, the oldest unless a column sort says otherwise. Then Change selected runs … (to archive them) or Delete … in the Actions menu. Runs of a job run more than once are its history, not mistakes: archive those rather than delete them.
Read more: Change many jobs at once · Run History
How do I see only the latest run of each job?
Latest run per job beside Duplicates in the Run History tab bar is on when the app opens: each job shows only its newest run among those the other filters let through. With Mode set to Discovery, that is each job's latest Discovery run. A run you have pinned shows too, whatever its age. With the switch off, a small green star at the end of a run's title marks its job's latest run. The Dashboard's Runs in Run History box has the same switch, and counts them.
Read more: Run History · Dashboard
Can I archive a job's old runs and keep the job?
Yes. Jobs and runs are archived independently: archive the runs that are done on the Run History tab — handy for a job that runs every day — and the job stays in everyday work and keeps running.
Read more: Run History · Jobs and job modes
Why would I run the same job more than once?
A Migration job, to migrate incrementally: each run brings over the files that are new or have changed since the last one. That is the default — Add New Overwrite Existing By Newer — and you can fine-tune it, for example Add New Only to bring in new files and leave updated ones as they are. A Discovery job, to look at the source again: with other filters — a size or a date range — or simply later on, to see how it has changed over time. Each run gets its own Run History row and report.
Read more: Rules for adding and overwriting files · Run History
Can I change a job and run it again?
Yes, as often as you need — for example a Discovery whose filter was too narrow. Change the job and set it to Ready: each run gets its own Run History row and report, and the earlier ones stay as they were.
Read more: Run History
What does a Run History row record?
The job's title, group and tags, mode, status and result, times, counts, messages, source, destination and a link to its report.
Read more: Run History
Why do a run's Files leave out the unchanged files?
The Files, Volume, Versions and Version volume columns count what changed: the files new to the BI data and those modified in the source since it last held them. A Discovery run also reports the files it found unchanged; rest the pointer on the run's title or one of its figures, and its card shows New, Modified and Unchanged apart, with their total — as does the Outcome section of the run's details. A file share has no version figures.
Read more: Run History · Discovery
What does the (Run: 3) at the end of a run's title mean?
It is the run's number among its job's runs in the same mode: (Run: 3) on a Migration run is the job's third Migration run. Discovery, Migration, Test Migration and Import runs each count from 1 on their own. The number is given as the run starts and never changes, and a copied job starts at 1 again.
Read more: Run History
Does archiving or deleting a run change the BI report?
Archiving does not: the run's data stays in the BI report. Deleting does: the files the run recorded are taken out of the report, as the SMART Migration server purges the run's data from the reporting database on its next check, some time after the click. While deleted runs are still to be purged, the mark on the Dashboard's Power BI heading turns red and shows how many; refresh the report once it is back to a green Up to date.
Read more: Run History · Dashboard
Why does deleting a run purge fewer files than it found?
A file belongs to the run that last reported it in the BI data. If run 1 found 10 files and run 2 found 3 of them changed, deleting run 1 purges only 7 — the 3 changed files stay with run 2, and in the report.
Read more: Run History · Business intelligence with Power BI
Why should I not delete Run History rows?
They are the migration's record; deleting one also purges its data from the reporting database.
Read more: Run History
Can old runs be deleted automatically?
Yes: give the job a Retention schedule in Advanced Settings. Every hour, its runs that finished longer ago are deleted as Delete … does, BI data included; a run any administrator has pinned is kept.
Read more: Run History · The job dialog
What is the difference between a Warning and an Error result?
Warning: the run did its work but met something to check. Error: something stopped it. Rest the pointer on the result in Run History for a card that says what the run reported and what to do; a click pins it, with the run's details and session log a button away.
Read more: Run History
What can I change on a Run History row?
Only how it is organised: My note, its tags, its pin and whether it is archived. What the run did — its settings, result, counts and report — stays as it was.
Read more: Run History
Does a run keep the job's settings when the job is changed later?
Yes. A run keeps a snapshot of the configuration it ran with.
Read more: Run History · Run details and the session log
How do I find the runs with the most file issues?
Pick With file issues in the filter under Result: it shows every run that recorded file issues, the most first, whatever its result.
Read more: Run History · File Issues
Run details and the session log
Section titled “Run details and the session log”These questions are explained in full in Run details and the session log
How do I read the log of a run?
Open the run's details and choose the Log tab.
Read more: Run details and the session log
What does SPO Rate Limit Delay mean?
The delay Microsoft 365's rate limits imposed on the run. Spread large jobs out over time.
Read more: Run details and the session log
How do I export the log as a spreadsheet?
Export to Files on the Log tab saves it as an Excel workbook in the run's folder.
Read more: Run details and the session log
How do I step through the runs without closing the dialog?
Previous run and Next run in the run details dialog. With a change waiting, save or cancel it first.
Read more: Run details and the session log
Can I rename a run without renaming its job?
Yes. Change Title — or Description, Job Group and Tags — in the run's details and click Save. Only the run changes, and its number stays on the end of its title. The BI report takes the new title once SMART Migration has written it on its next check.
Read more: Change a run's title, description, group and tags
Do a job's runs take its new title when I rename the job?
If you say so. After you rename a job in the job dialog and Save, the app asks about its runs that still carry the old title: Yes, rename them gives them the new title, each keeping its number. A run you renamed in its own details keeps its title, and a run still under way follows the job at once.
Read more: When the job is renamed
How do I find a run's session on the SMART Migration server?
Copy the SMART Migration SessionLogId from the foot of the run's summary card or from its details, and look it up on the SMART Migration server's dashboard with Find job session criteria. The SMART Migration Task Name is the task in the server's scheduler that ran the job. Both are for technical tracking and analysis: a session that ended successfully keeps no log on the server — its log is on the run's Log tab.
Read more: Run details and the session log
Reports and run folders in Nextcloud Files
Section titled “Reports and run folders in Nextcloud Files”These questions are explained in full in Reports and run folders in Nextcloud Files
Where are a run's report and log kept?
In a folder of its own for each run, under the job's folder in the Jobs folder of the Team Folder SMART Migration Reports in Nextcloud Files. When the run has any, Open in its Reports column goes straight there.
Read more: Reports and run folders in Nextcloud Files
Why can I not see the reports in Nextcloud Files?
Only members of the group SMART Migration Reports see that Team Folder. The app adds an administrator when they open it; anyone else is added by an administrator, in Nextcloud's Accounts settings.
Read more: Reports and run folders in Nextcloud Files
Can I rename the SMART Migration Reports folder?
Yes. The app follows the Team Folder by its ID.
Read more: Reports and run folders in Nextcloud Files
What happens to a job's report folder when I change its title?
Nothing: the folder keeps the name it was created with, such as Finance library (ID-7). The job's later runs still go into it, recognised by the (ID-7) its name ends with, and the Reports links still open it.
Read more: Reports and run folders in Nextcloud Files
When is a run folder removed?
Only with its Run History row, once SMART Migration has purged the deleted run.
Read more: Reports and run folders in Nextcloud Files
What do (Run-3) and (ID-12) in a run folder's name mean?
(Run-3) is the run's number among its job's runs of that mode — the (Run: 3) on its title in Run History. (ID-12) is the run's ID, which keeps the name unique and is how the app finds the folder again.
Read more: Reports and run folders in Nextcloud Files
File Issues
Section titled “File Issues”These questions are explained in full in File Issues
Why was a file not migrated?
The File Issues tab lists it, with the reason in its Error Message column — such as a blocked file type or metadata the destination will not accept.
Read more: File Issues
How do I see the issues of one run?
Click the issues mark and count beside the run's Result in Run History. The File Issues tab then shows only that run's issues, under a frame naming the run, until you click Show all issues.
Read more: File Issues
How do I fix an issue and migrate the file after all?
Fix the cause at the source, then run the job again; the default rule adds what is missing.
Read more: File Issues
Why is the same file listed twice?
A later run reported the same problem again. Pick both Same Filename and Same path in Duplicates, then Select duplicates to clear them.
Read more: File Issues
See also
- Nextcloud FAQ — every group of questions