Running missed schedules

Because scheduled tasks may be missed when the Batch Manager server is offline, you can configure the Batch Manager to search for missed schedules on startup. To search for missed schedules, edit the BatchManager configuration in the Configuration Editor. On the SERVERSETTINGS node, set the Invoke Missed Schedules on Startup attribute to True. The Missed Schedules Seconds attribute specifies how many seconds back the Batch Manager will search for missed schedules.

To identify missed schedules, the Batch Manager queries past schedules on startup, searching back the number of seconds specified in the configuration. For each schedule, the Batch Manager compares the last invocation date in the CORE_BATCHPROCESSING.SCHEDULE table to the next scheduled date in the RESOURCES.TIMESCHEDULE table. If the last invocation is less than the next scheduled date, this indicates that the task was missed.

For example, suppose the Batch Manager starts at 2:00 PM and is configured to search back one hour for missed schedules. If a schedule is found with a last invocation date at 1:15 PM and a next scheduled date at 1:30 PM, this indicates that the task was supposed to run at 1:30 PM, but didn't. Therefore, the Batch Manager will run the task.