Notifications when a job runs

How a notification reaches people

The app hands each notification to Nextcloud's Notifications app, which delivers it the way each person has chosen. The app itself contacts nobody: delivery is Nextcloud's own.

Where it shows	What it takes
The bell at the top of Nextcloud	Nothing: every notification is listed there.
Browser push	Nextcloud open in the browser, with notifications allowed for the site.
Phone push	The Nextcloud app on the phone, signed in to this Nextcloud.
Email	Email reminders turned on in the member's own Personal settings under Notifications, and an email server set up in Nextcloud's Basic settings.

A notification carries the SMART Migration logo in colour, the job's title and, on the line under it, a coloured mark for what happened: green for Ok, yellow for Warning or red for Error when the run ends, orange for Canceled, blue for Started, and red for First error or yellow for First warning while it runs. Under it, on one line, the message behind it — The job has started successfully. for a start, the log row's own text for an error or a warning, the run's summary or error message when it ends — and then the job's group, how long the run took once it has ended, and the run's counts of files, versions, errors and warnings. Last, each on a line of its own, come the run's Source and Destination — the library's URL or the file share's UNC path; a web address is a link that opens it. A Discovery run, which writes nothing, has no destination line. Clicking the notification, or its Open run in SMART Migration button, takes you to the run's row in the Run History table, ticked, marked and scrolled into view; a double-click opens its details. If the run has been deleted since, a message says so. Only administrators can open that page, so notify administrators.

Every notification sent is recorded and shown on the Dashboard, under Notifications sent: one row per job, its latest notification — when, about which run, what it said, and which users it went to — and the card on its Event, Message or Sent to names who it went to and lists every notification of that run and the job's earlier runs. Each row is a click from its run and its job, and the table can be filtered by any of them.

Managed like every Nextcloud notification

They are native Nextcloud notifications, not something of the app's own, so each person manages them the way they manage every other notification in Nextcloud:

Dismiss one in the bell with its ×, or all of them with Dismiss all.
Email: how often unread notifications are sent by email — or never — is each person's choice in Personal settings → Notifications.
Browser and phone: the browser's permission for the Nextcloud site, and the notification settings of the Nextcloud app on the phone, decide whether they pop up there.
Do not disturb: a person whose status is set to Do not disturb gets no pop-ups; the notifications still wait in the bell.

Whom a job notifies is the job's own Notify to, below; what it notifies of, its own boxes.

Choose who is notified

Each job sends its notifications to the Nextcloud users and groups chosen in Notify to right under its Notifications boxes — any mix, up to 25. A group reaches every member it has when the notification is sent, and each person gets a notification once, even when they are chosen by name and are in a chosen group too.

Start from yourself
A new job starts with you, the administrator creating it, in Notify to — and so does an Import job's Job defaults. Tick a box on a job that has no one chosen, and you are chosen.
Pick someone else
Type in Notify to to search the users and groups by name, and pick as many as you need: each shows as a chip — a user with their picture, a group with the group mark — and its × takes it off.
Notify a team
To tell a team that changes over time, make a group in Nextcloud's Accounts page, for example Migration team, add the people who follow the migration, and pick that group beside anyone else.

The Jobs table shows the first of a job's recipients in its Notify to column while a box is ticked, with how many more there are; its tooltip and the job's pinned card name them all.

Choose what a job notifies

Each job decides for itself, under Notifications in the Job step of the job dialog, right below Job Status, shown with Advanced Settings on. Every box is ticked on a new job, with you in Notify to; clear the ones you do not want. A job an import writes takes its boxes from the Import job's Job defaults, also all ticked on a new Import job. Each box is an event of its own.

A ticked box needs someone in Notify to

A job with any of its boxes ticked and no one in Notify to does not validate, and so cannot be set to Ready: the Jobs table's Notify to column says No one in red. Choose a user or a group, or clear the boxes. The same holds for the boxes on an Import job's Job defaults.

Box	Sends a notification
Job start	When SMART Migration picks the job up and its run starts.
Job finish	When a run ends, named by how it ended: finished, finished with warnings, finished with errors, or canceled.
First warning	The moment a run logs its first warning, with the warning's text.
First error	The moment a run logs its first error, with the error's text.

Errors and warnings arrive while the run is still going

An error or a warning is sent as SMART Migration writes it to the run's session log, not when the run ends — so a long run that hits a problem is known about at once. Each is sent once per run: the run's later errors and warnings send nothing more, and its session log in Run History holds them all.

Many jobs at once — tick them on the Jobs tab, choose Change selected jobs … in the Actions menu and switch on Notifications: it sets the four boxes and Notify to on every ticked job. The dialog opens with each box as the jobs have it now — ticked where every one of them has it on — and with their users and groups when they share the same ones, you otherwise — Apply puts that list in place of each job's own; so for one job, from its row or its pinned card, it shows what that job was saved with.
Copy gives the copy the same boxes and the same users and groups as the job copied.
A user or group deleted from Nextcloud is skipped: the others on the job are still notified, and the job still saves as it is.
A run deleted from Run History takes its notifications with it.

Import jobs

An Import job has two sets of boxes, each with its own Notify to. Notifications, in the Job step, is about the Import job's own runs. Notifications on Job defaults holds the boxes and the users and groups every job the import writes is given.

When no notification arrives

Check these in order:

Check	Where
It was sent	Notifications sent on the Dashboard: listed there means Nextcloud was handed it.
The job notifies that person	`Notify to` in the Job step of the job dialog, or the job's `Notify to` column.
The person is in that group, when a group is chosen	Nextcloud's Accounts page.
The job has the right box ticked	Notifications in the Job step of the job dialog.
The run logged an error or a warning	The Log tab of the run's details in Run History. An error or a warning already sent for the run is not sent again.
Email reminders are on, and Nextcloud can send email	The member's Personal settings, and Basic settings for the email server.