Downtime and clock changes

No jobs are scheduled during the time that passed since the previous shutdown. For example, if KCM Document Processor Manager is stopped every night at 23:00 and restarted at 01:00, the daily job will never be executed and the DailyTask.dss exit point will never be called. In such a situation, you can use the HourlyTask.dss script to perform any daily tasks at a more appropriate time.

If the clock on the server is set forward while KCM Core is running, internal jobs are scheduled in quick succession for each hour and midnight event in the skipped interval. It can take a couple of minutes before a clock change has been detected and the scheduled job for the skipped interval is run. If the clock on the server is set back, the scheduling is not changed and no internal jobs are scheduled until the clock passes the original time again.