How offline clocks are uploaded to WFM

After the connection has been re-established, the user's device is interrogated to determine whether offline clocks exist on that device. When offline clocks are found, WFM tries to create a pending clock record for each offline clock found on that WFM instance. If the data related to an offline clock is insufficient or has been corrupted, WFM logs an exception and continues iterating through any relevant offline clocks still on the user's device.

After the pending clock records have been created for processing, the offline clocks stored on the device for that instance are deleted, including any invalid clocks. The user is not informed that these actions have taken place.

Offline clocks converted to pending clock transactions are not limited to the specific user who is currently logged in at the device. For example, if multiple employees record offline clocks using a shared device, all of the valid offline clocks are converted to pending clocks regardless of the employee who is using the device when the connection has been restored.

The processing of the pending clocks into the timesheet occurs at the interval defined within the Process Clocks task found in the Job Scheduler.