Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article provides a resolution for the issue where the warning and failure timing calculations are incorrect.
Scenario 1: Some SLAs don't take into account daylight saving time for the warning and failure duration
This issue may occur when warning and failure duration times don't consider daylight saving time for the service-level agreement (SLA) in Omnichannel for Customer Service.
Cause
If your SLA was created in the web client that's now deprecated, the business schedule calendar doesn't support daylight saving time.
Resolution
To use the daylight saving time functionality and many other new features, migrate your SLAs created in the web client to Unified Interface. For more information, see Migrate automatic record creation rules and service-level agreements.
Scenario 2: An SLA KPI instance shows a difference in Failure Time and Warning Time
By default, SLAs in the Succeeded and Non-compliance terminal statuses aren't reevaluated when the success condition changes, and they can't be paused or resumed.
Cause
The Failure Time and Warning Time of the slakpiinstance
are calculated based on the time zone used in the SLA calendar.
If the calendar time zone differs from the end user's time zone, the calculation is made based on the calendar time zone, and the user may see a difference.
Resolution
Make sure the end user's time zone matches the calendar time zone. For more information, see Understand time calculation of SLA KPIs.