Interpreting the Scheduler Log
The Scheduler Log contains information about each task that is run.
The most recent event is at the top of the log.csv file.
Each line of the log displays a summary in the Log Type column of what occurred.
Reading from the bottom of the log upwards and examining the dates and times, that the task was scheduled for execution a number of days before it was run. The log activity for any successful execution of a task is as follows:
Task execution commences
Pre-task actions are run
Task components are run
Post-task actions are run
Task execution completes
Completion status is logged
Task is rescheduled
In the previous log, which contains the results of the 'Example of a Successful Import Batch' task, the first import specification creates only a single statistics line. From this, it can be concluded that the import specification is importing entity records. The details for the statistics show the number of entities that were added, updated, unchanged, or were in error. The second import specification creates three separate statistics lines: it can be concluded from this that the import specification is importing link records. The statistics show the number of entities or links that were added, updated, unchanged, or were in error for the links, end 1 entities, and end 2 entities.
Note: A task does not run if a user changes an import or export specification within the batch that requires a response from the user. Changes of this type would be an import specification that prompts for confirmation of the action to take when a matching entry is found in the database or an export specification that relies on a parameterized query.
If a pre-task plug-in, post task plug-in, or component fails to complete successfully the task execution stops at that point and the completion status indicates that a problem was encountered. The log does not report on any pre-task or post-task programs that fail to complete.
Pre-task action errors
The following example log shows that a problem was encountered when a pre-task action is run:
Date & Time | Level | Description | Connection Name | Task Name | Task Type | Trigger Name | Trigger Type | Log Type | Module |
|---|---|---|---|---|---|---|---|---|---|
2024-09-14 11:31:05 | Info | Task scheduled to run at 14/09/2024 11:31:35 | User Guide DB | Example Pre-Task Error | Batch Import | Daily import 11:30 | Interval | Schedule | i2.Base.Apps.Scheduler.Service.Schedule |
2024-09-14 11:31:04 | Info | Starting execution of 'Batch Import' | User Guide DB | Example Pre-Task Error | Batch Import | Daily import 11:30 | Interval | ExecuteTask | i2.Base.Apps.Scheduler.Service.Schedule |
2024-09-14 11:31:04 | Info | Starting execution of pre-task program 'example.exe' | User Guide DB | Example Pre-Task Error | Batch Import | Daily import 11:30 | Interval | ExecuteTaskAction | i2.Base.Apps.Scheduler.Service.Schedule |
2024-09-14 11:31:04 | Error | System.ComponentModel.Win32Exception:The system cannot find the file specified | User Guide DB | Example Pre-Task Error | Batch Import | Daily import 11:30 | Interval | Error | i2.Base.Apps.Scheduler.Service.Schedule |
2024-09-14 11:31:04 | Info | Failed to execute pre-task program 'example.exe' | User Guide DB | Example Pre-Task Error | Batch Import | Daily import 11:30 | Interval | ExecuteTaskAction | i2.Base.Apps.Scheduler.Service.Schedule |
2024-09-14 11:31:04 | Info | Completed execution of 'Export Batch Specification Example' | User Guide DB | Example Pre-Task Error | Batch Import | Daily import 11:30 | Interval | ExecuteTask | i2.Base.Apps.Scheduler.Service.Schedule |
2024-09-14 11:31:04 | Error | Errors detected during task execution | User Guide DB | Example Pre-Task Error | Batch Import | Daily import 11:30 | Interval | CompletionStatus | i2.Base.Apps.Scheduler.Service.Schedule |
2024-09-13 14:03:26 | Info | Task scheduled to run at 13/09/2024 14:04:00 | User Guide DB | Example Pre-Task Error | Batch Import | Daily import 11:30 | Interval | Schedule | i2.Base.Apps.Scheduler.Service.Schedule |
Log management
The default NLog configuration for the Scheduler is to show today's entries in the log.csv file. Older log entries are archived into log.date.csv. files. After 30 days the archived log files are automatically purged. You can change the default settings in the NLog.config file.