Scheduler timing
In Varicent Incentive Compensation Management (ICM), you might find that a scheduled process doesn't run at exactly the time that you specified in the Scheduler module. The discrepancy might be caused by time changes in the system.
For example, you might set a process to run at exactly 11:00 p.m. The next day, you might notice that the Scheduler module log file shows that the item ran at 11:02 p.m.
This discrepancy might be caused by time changes in the system because, as an example, Time Services periodically makes minor adjustments to the system time. These adjustments can interfere with processes in the Scheduler module running at exactly the specified time.
Scheduler time conflicts
In Varicent Incentive Compensation Management (ICM), when you schedule tasks in the Scheduler module, remember that two tasks cannot run at the same time.
For example, if one process is scheduled at 11:00 p.m. and another process is scheduled at 11:01 p.m., the second process won't run if the first isn't completed. If the second task can't run, an error message is displayed to indicate a scheduling conflict. The conflict must be resolved before the second task can run successfully.
The Scheduler module has a 10-minute window to run the task before it's skipped. For example, if the Scheduler module misses a 11:00 p.m. scheduled time due to a scheduling conflict, it continues to try to run the task until 11:09:59 p.m. If the task can't run in the 10-minute window, the task will be skipped.
Important
The Scheduler module service can run only one process at a time. If more than one model uses the same service, scheduled processes must occur at different times for each model. If scheduled model administration must occur simultaneously on more than one model, each model must point to a different service.