The Details tab
Section titled “The Details tab”| Section | What it shows |
|---|---|
| Job | The run's own Title, Job Group, Description and Tags — as the job had them when it ran, until you change them here — and its Archived switch. |
| Action | Mode, Status and Result. |
| Outcome | Job Start, Job Finished, Duration (< 1 min for a run shorter than a minute), File Count, Versions, Volume, Version volume, Issues Count, Source converted to .url, SPO Rate Limit Delay, the Summary and the Progress reported while the run was under way. File Count, Versions, Volume and Version volume are the new and the modified files together, as in the Run History table; under the boxes a small table shows them apart — New, Modified and, for a Discovery run, Unchanged, with their Total — the parts on a yellow band under the heading Compared with the BI data, with lines under the table saying what each part is, and Total apart from them: the same table the run's summary card shows. A count of none — files, versions, volumes or issues — is left blank rather than shown as 0. A file share keeps no version history, so its runs show no Versions or Version volume at all. A volume reads in MB, GB or TB; one too small to show as a whole megabyte reads in KB, and one under a kilobyte as < 1 KB. A Job Import run shows Imported jobs instead of the file figures: the group its new jobs were filed under, as a link that opens the Jobs tab with only that group showing. |
| Source and destination | Where the run read from and wrote to, and their types. The source is on one line: rest the pointer on it to read the whole of it, and the copy button beside it puts it on the clipboard. |
| Configuration details | The job exactly as it was configured when this run claimed it. |
| Miscellaneous | The run's folder in Nextcloud Files. |
| SMART Migration | The report, the Task Name, the SessionLogId and the Windows process ID. |
| App | The Job ID and the Run History ID. |
Change a run's title, description, group and tags
Section titled “Change a run's title, description, group and tags”Title, Description, Job Group and Tags are the run's own: changing them changes this run only — the job keeps what is defined on it, and its later runs take that. Job Group is a list of the groups, as in the job dialog, with Manage groups beside it to add or rename one on the way. The run's number stays on the end of its title, such as (Run: 3), whatever you rename it to. Archived puts the run away out of everyday work; it stays in Run History and in the BI data. My note about this Run, under Description, is your own note on the run — other administrators do not see it, and it never reaches the BI data. Description is drawn in blue and the note in orange, each with the small triangle that marks it on the run's title in the table.
Nothing is written until you click the green Save button at the foot of the dialog; Cancel closes it and leaves the run as it was. While a change is waiting, Previous run and Next run wait too: save or cancel it first.
When the job is renamed
Section titled “When the job is renamed”A run takes its job's title when it runs, and a run still under way follows a rename of its job at once. When you rename a job in the job dialog and Save, and some of its finished runs still carry the old title, the app asks whether they should take the new one: Yes, rename them gives them the job's new title, each keeping its own number, and No, keep their title leaves them as they are. A run whose title you changed here is not one of them, and keeps its own title. Runs renamed this way reach the BI report as any change made here does — see below.
The change reaches the BI report on SMART Migration's next check
Section titled “The change reaches the BI report on SMART Migration's next check”A saved title, description, group or tags is written into the BI data by the SMART Migration server on its next check, and the report shows it once SMART BI.pbix is refreshed after that. Until the server has caught up, an amber mark on the Dashboard's Power BI heading says how many changed runs are still to be updated. In Run History, such a run shows a small yellow triangle in the top-left corner of its title, and its summary card says why; the triangle goes once the server has written the change. A Job Import run holds no BI data, so nothing waits for it. See Refresh, upload and share SMART BI.pbix
At the foot of the dialog, Copy link copies a web address that opens this run; rest the pointer on it for who can use the link — anyone else with access to this app.
- SPO Rate Limit Delay shows the delay Microsoft 365's rate limits imposed on the run. Microsoft 365 slows down heavy or frequent reads, so a high delay is a reason to spread large jobs out over time rather than a fault in the job.
- Source converted to .url shows Yes when the run replaced the SharePoint files it migrated with .url links to Nextcloud, and is blank otherwise. See Cutover: Traditional and Enhanced Migration
- Configuration details cannot be edited: it stays the account of what this run actually did, even after the job is changed.
The Log tab: the session log
Section titled “The Log tab: the session log”When the session holds an error, the Log tab shows the red error mark beside its name; when it holds a warning and no error, the amber warning sign — so you see it from the Details tab too. Rest the pointer on the tab to read how many of each. The Log tab lists the messages SMART Migration logged during the run, one row each, with its number, time, category, class and object, and the message itself. Select a row to read its full message below the table, and Copy message to put it on the clipboard.
- Category marks what matters as a pill: the session's start in blue, errors in red and warnings in yellow, and the closing row in the session's outcome. On a canceled run, the row that says so and the closing row both read
Canceledin yellow. - Filter messages shows the rows that contain a text.
- Show all adds the detail messages. Without it, the log shows the main messages and every error and warning.
- The SMART Migration SessionLogId names the session the run belongs to. When SMART Migration ran several jobs in one session, their runs share the session and its log.
Task Name and SessionLogId on the SMART Migration server
The SMART Migration Task Name (such as Job Thread 1) is the name of the task in the scheduler on the SMART Migration server that ran the job. The SMART Migration SessionLogId (such as 6wj4_ee_d) finds the session on the server's dashboard with Find job session criteria. Both are for technical tracking and analysis: a session that ended successfully keeps no log on the server, and its log is on the run's Log tab. The run's summary card on the Run History tab shows both at its foot.
Export the log as a spreadsheet
Export to Files saves the whole log into the run's folder in Nextcloud Files as an Excel workbook (.xlsx), named after the run, such as Log - Finance library 2026-09-26 07.59.xlsx. It opens as a table, with a filter on every column and a frozen header, and its times are real dates, so the log of a long run can be sorted and searched. When a run finishes, its log is exported on its own; export it again only if more messages have been added since.
Move between runs
Section titled “Move between runs”Previous run and Next run step through the runs in the order the Run History table shows them, without closing the dialog. Goto Job definition takes you to the row of the job the run was made from in the Jobs table, Reports opens the run's folder in Nextcloud Files, and Copy link gives a link that goes straight to this run's row.
See also