Desktop: Client's system clock should be synchronized to the Finesse server system clock.
Client's system clock should be synchronized to the Finesse server system clock
|Problem Summary||Fields that display a duration on the Finesse gadgets will have incorrect values unless the system clock on the agent or supervisor desktop is synchronized with the Finesse server system clock. This does not apply to different time zones between machines - only when the minutes/seconds are different.|
|Possible Cause|| For fields that display a duration, such as the Time in State field in the Team Performance gadget and the Max Time field in the Queue Statistics gadget, Finesse server publishes a time stamp which gets converted to a duration on the agent or the supervisor desktop, based on the current time minutes on the agent or supervisor desktop. Therefore, if the system clock on the agent or supervisor desktop is not synchronized with the system clock on the Finesse server, the duration will be incorrect.
The server publishes the timestamps in UTC format and the client converts it into the local time zone and then computes the duration based on the current local time. The server and client need not be in the same time zone. The clocks must be synchronized i.e., if the server is 3pm in CA then the agent PCs in NY should be 6pm, not 6:03pm or 6:05pm.
|Recommended Action||Synchronize the system clock on agent and supervisor desktops to the Finesse server system clock. Use a common NTP server between server and client.|
|Associated CDETS #||N/A|