How to troubleshoot SLA Warning Notifications showing incorrect percentages - Support and Troubleshooting

How to troubleshoot SLA Warning Notifications showing incorrect percentages Issue  When using Service Level Agreement (SLA) calculated values in a task_sla email notification, inaccurate values are sent out in the resulting emails. For example, a SLA Percentage Timer is set up to fire at 75% completion of an SLA. This activity calls another activity that creates a sla.warning event that fires an email notification. The subject line of the SLA notification is set to the dynamic value ${business_percentage} and t he resulting emails show a value other than 75%.

Cause The Workflow Percentage Timers and the SLA Calculations are completely independent of each other. Using ${percentage} in a notification will only ever display the most recently calculated value of the task_sla.

Note : SLAs are calculated on a scheduled basis, and progressively more frequently the closer they are to their planned end time. For more details on how SLAs are calculated, refer to SLA Automation in the ServiceNow product documentation.

The Calculate SLAs on Display (glide.sla.calculate_on_display) runs the calculation of SLAs when a task record is viewed to display real-time numbers (percentages, time used, and so on). To perform the calculation, this property imposes an overhead necessary on a case-by-case basis. If the [glide.sla.calculate_on_display] property is turned on, SLAs are calculated when the case form is viewed. This does not mean that SLAs are updated when a report is run or a case is viewed in a list.

If this property is turned on, the SLA updates when the case form is viewed. For performance reasons, SLAs cannot be calculated on demand. By default, this property is turned off, meaning the business elapsed time and all other calculated fields will only ever represent the values from the last time the SLA was calculated.

Resolution To specify elapsed percentage in SLA notifications, it is recommended to use notifications for each percentage level. For example, an email notification for " 75 percent SLA Warning" is created and a special event is used to trigger that notification. The event can be called "sla.warning.75".

Another way to accomplish this is by calling the code directly to update the SLA before sending the notification. Using code similar to the Run SLA Calculation UI Action can do this.