Stephen - You are correct that Scheduler logging is currently very granular and somewhat primitive/non-configurable from the perspective of high-volume Publishers like yourselves.

The workaround at the moment is to use an external scheduler like the Windows Task Scheduler, or else create your own job-oriented monitoring log file by defining Task List Actions on success or fail that write logging info to an external text file using a Command Action.

This would result in a condensed log file with only one text line per task, which could in turn be imported into/appended to an Omniscope IOK monitoring file and text mined/parsed for warnings, errors etc., setting flags in formula fields for review and triggering alert actions like e-mail...

Do you have an example or documentation around scheduling using Windows Task Scheduler?

The Scheduler logging has improved a lot in version 2.8, but to schedule task reporting via the Windows Task Scheduler, you will need to use the Windows command syntax documented at the end of this page:
http://www.visokio.com/kb/xml-actions

Good to know... we are looking at an upgrade over the holidays

Hi Thomas,

When we run the Scheduler as a Service and review the log file, we don't see the daily tasks added to the log file? Is this expected?

When I open the Scheduler application, the log file states that the Scheduler is already running and it starting in configuration-only mode. Is there a way to open the first instance of the Scheduler? Our expectation is that the log file should capture all tasks when using the Service regardless of if the Scheduler configuration application is open or not.

To see more information about the tasks being executed by the Scheduler, turn on "Log Detail" option in the Omniscope Server/Scheduler configuration.
See attached screenshot.

As per my evidence Scheduler is not working in my installation. I turned Log Detail on but I have no evidence in the log about any activity on the scheduled tasks. The service is active but I believe the Scheduler is not executing the planned tasks.

As per last customer message, the Scheduler log showed that the IOK file was not present. It was a Windows System account problem. Fixed by the user.