Service Level Agreements (SLA) notifications are getting triggerred for wrong percentage timingsIssue The breach notification for Service Level Agreements (SLA) for Standard Changes has been sent with the wrong SLA percentage. While the breach notifications that are triggered from the Default SLA workflow for Incidents and Catalog tasks are functioning correctly, they are not working properly for Standard Changes.CauseIt appears that the problem lies in the use of Relative Duration in the Service Level Agreements (SLA) definition. This is causing the schedule of the Service Level Agreements (SLA) to be recalculated, even though a schedule has already been defined in the Service Level Agreements (SLA) definition.ResolutionIt has been determined that there is no need to incorporate a schedule in the script of the Relative Duration. This is causing unexpected results, particularly when creating SLAs that are not within the specified schedule. The solution was to remove the Schedule portion of the script from the Relative Duration, after which the issue was resolved and no longer observed.Related LinksKB0520314-How to troubleshoot SLA Warning Notifications showing incorrect percentages