KB16292: The scheduled Data Load of MicroStrategy Enterprise Manager 9.x appears to be off schedule or runs behind the defined schedule

• Strategy

This document explains why the scheduled Data Load of MicroStrategy Enterprise Manager 9.x may be offline and suggests steps to resolve this problem.

SYMPTOM:
The Strategy Enterprise Manager 9.x scheduled Data Load appears to be off-schedule or running behind the desired schedule. For example, the data load is set to run every six hours at 12am, 6am, 12pm, and 6pm. However, it is observed to run at 3am, 9am, 3pm, and 9pm - three hours off schedule.
The Strategy Enterprise Manager 9.x data load schedule is setup correctly and shows the desired schedule, as shown below:

In this example, the data load is running every six hours as desired, but the data load is occurring three hours late.

CAUSE:
This issue is caused by an incorrect initial setup of the scheduled data load. One important facet of the data load schedule is that it does not reset itself every night to comply with the Time Range setting. The data load is strictly governed by the recurrence frequency setting, or the time between data loads, in this example, 6 hours. The next data load will not occur until the point in time where the current time is equal to the last data load start time plus the frequency.
Next data load Time = 'Last data load start time' + Frequency
Only scheduled data loads will modify the 'Last data load start time' value. This means that running a manual or custom time window data load will not affect the schedule.
Consider the following three scenarios, using the schedule defined above.
Scenario 1: A manual or custom time window data load has no effect on the scheduled data loads.

Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.
Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.
Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.
Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.

Scenario 2: A failed data load does not affect the data load schedule.

Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.
Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.
Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.
Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.

Scenario 3: Restarting a stopped schedule will immediately kick off a data load if the 'Last data load start time' plus Frequency is less than the current time.

Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.
Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.
Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.
Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.
Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.
Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.	Google Map in VIGoogle MapApple MapGoogle Map in RSDGoogle MapApple MapESRI Map in VIESRI MapApple MapESRI Map in RSDESRI MapApple Map in 10.1 (showing Grid in 10 and lower)TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user wakes up and decides to trigger a manual or custom time window data load at 5am, 1 hour before the next scheduled data load.Because this is a manual or custom time window data load, the 'Last data load start time' is not affected.6amAt 6am, the scheduled data load kicks off, not affected by the manual or custom time window data load.The 'Last data load start time' is 12am, the frequency is 6 hours, so the data load is triggered as desired.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amAn administrative user shuts down the intelligence server for maintenance.The data load schedule is not stopped.6amThe Intelligence Server is still shut down. At 6am, the scheduled data load kicks off, but fails.Because the data load kicked off, the 'Last data load start time' is set to 6am, the frequency is 6 hours, so the next data load will occur at noon. If the Intelligence Server is up and running at noon, the data load will migrate data over the entire time period since the last successful data load finish time.TimeEventDetails12amA scheduled data load occurs at 12am as desired.The 'Last data load start time' is set to 12am.5amThe data load schedule is stopped by an Administrator for system maintenance. 6amAt 6am, nothing happens.The data load schedule is still stopped.9amMaintenance finishes and the data load schedule is started again. 9am and 1 secondThe data load schedule process checks, and finds that the 'Last data load start time' plus 'frequency' is less than the current time, so the data load kicks off immediately.The data load kicks off immediately, setting the 'last data load start time' to 9am.

Note that from now on, the data load is seemingly running three hours behind schedule, at 9am, 3pm, 9pm and 3am. This off-schedule pattern can occur in many different ways, such as defining and starting the Strategy Enterprise Manager 9.x data load schedule for the first time at 9am, when the 'start date' is today or in the past. The data load would then kick off immediately, appearing to be off-schedule from the start.

ACTION:
Users must pay careful attention when stopping or starting the Strategy Enterprise Manager 9.x scheduled data load. To get the data load back on the desired schedule track, stop the data load for a period of time longer than the frequency, and then start it at the correct time.
Continuing from scenario 3 above, the 'Start Date' setting can be used to accomplish this:

A minimum of 6 hours (the frequency) prior to midnight (the start time), stop the data load.
Set the 'Start Date' to be tomorrow.
Apply changes and start the schedule.
This way, the data load frequency + 'Last data load start time' is now some time before 12am tomorrow. When 12am comes the data load will check, and seeing a time less than 12am, it will trigger a data load immediately and the data loads will be back on the desired schedule.

Comment

0 comments

Details

Knowledge Article

Published:

March 31, 2017

Last Updated:

March 31, 2017