Daily tasks fail to start when scheduled

You need to determine why daily tasks fail to start when scheduled.

Unica Discover Session Archiving delays the start of a daily task until all sessions to be extracted were indexed into the Long Term Canister. Unica Discover Session Archiving inserts an extra time margin to ensure that any idle sessions in the canister expired.

Any Unica Discover Session Archiving daily task has an end time of 24:00, and the task cannot begin until one hour after the last session was indexed. This one-hour buffer ensures that all sessions marked as "closed" had time to be indexed. For a daily task that extracts yesterday's data (00:00 - 24:00 of the date before today), the earliest start time is 1:00 am.

In addition to the one-hour buffer, sessions do not close until the canister session idle time expired. If the session idle time is set for 30 minutes, the earliest executable start time is 1:30 am.

Suppose that the Nightly Extract is scheduled to run at 00:01 each morning. At 00:01 the Nightly Extract attempts to run and checks the session indexes.

  • The last indexed session time was 23:49:50 from the previous day, so the one hour buffer test that failed and the task is scheduled to run again at 01:01.
  • At 00:55, the Nightly Extract attempts to schedule a run at 01:01 and checks the session indexes. Since the last indexed session time was 23:59:43 from the previous day, the one-hour buffer test failed at the time of the test, and the task was scheduled to run again at 02:01.
  • At 01:55 the Nightly Extract attempts to schedule a run at 02:01 and checks the session indexes. The index test passes, and the task is scheduled and started at 02:01:01.
Note: To account for the processes of indexing sessions and canister session timeout settings, it is recommended that any daily tasks be scheduled after 02:00:00 each night.