Scheduled operations history

What this is for

Shows the recent runs and notes of scheduled file operations as recorded in the journal. Scheduled file operations are installed together with the Share Manager - one payload, no separate download and no Windows service - and run while the Share Manager runs in your signed-in session; they need no folder sharing, no server, no open port and no administrator rights. The window opens from 'History..' in the Scheduled operations window and on the 'Scheduled file operations' page of the Share Manager settings.

Scheduled operations history Scheduled operations history

In this order

  1. Read the list: Time, Operation, Startup and Result.
  2. Widen the window if a result is long.
  3. Press 'Refresh' to read the journal again.
  4. Press 'Clear history' and confirm to empty it.
  5. Press 'Close'.

The elements

Columns

Time, Operation (its name), Startup and Result. Startup is On schedule, Manual, Run all or Late, and stays empty for a note. The window reads the latest 200 journal entries when it opens and on 'Refresh'; it does not update by itself.

Results of a run

'Completed: N file(s)', with ', skipped: M' when some were left out and '(to the Recycle Bin)' for deletions. 'With errors: N; completed: M file(s)' followed by the first cause, such as a file in use, no access, a file not found or changed, or a full disk. 'Stopped: ..' when a wall ends a run, for example an unreachable folder, a resource without a stored password or with an unconfirmed server key, or a device that is offline. 'Not started: ..' when the definition is refused, 'Skipped: ..' and 'Interrupted'. The journal keeps codes, not raw error text, so the wording follows the current language. With Google Drive as a side, the cause can also be no connection with Google Drive, no room on it, a sign-out from it, or a file larger than a packet may be.

Notes

A row without Startup is a note: 'Skipped: the run time (..) passed while the manager was closed', 'Running late: the run was due at ..', 'Refused: this operation is already running or waiting in the queue' and 'Resumed: the cause of the stop is gone'.

Clear history

Asks 'Clear the history of scheduled operations? The operations and their schedules do not change.' with No as the default answer. It empties this journal only; the operations and their schedules stay. The button is disabled while the history is empty.

Manager settings · SFTP sharing settings · Exchange server settings