Service Level Agreements (SLAs)s are not attaching to Incidents even though the SLA conditions matchIssue Two Response SLAs did not attach to any Incident. But as per SLA definition of given SLAs they should get attached. CauseSLA Definition : SLA 1Start Conditions ( All of these conditions must be met ) :-----------------State is NewPriority is Priority 3Assignment Group is GROUPISDCaller.location is emptyLocation is not Digital--------------- Stop Conditions:-------------------State is one of- Assigned- Work in progress- Awaiting User info- Awaiting 3rd party- Awaiting Change- Resolved- ClosedORAssignment Group is GROUPISDAssignment Group is not empty---------------------------- SLA Definition : SLA 2Start Conditions ( All of these conditions must be met ) :-----------------State is NewPriority is Priority 4Assignment Group is GROUPISDCaller.location is emptyLocation is not Digital---------------Stop Conditions:-------------------State is one of- Assigned- Work in progress- Awaiting User info- Awaiting 3rd party- Awaiting Change- Resolved- ClosedORAssignment Group is GROUPISDAssignment Group is not empty---------------------------- The Start condition is a subset of the Stop condition e.g- Assignment Group is GROUPISD- Assignment Group is not emptyFor this reason, the Stop condition will always match when the Start condition matches and the SLA will never attach ResolutionThe SLAs did not attach because some of the Start Conditions match the Stop conditions.In this Case, the Stop condition will always match when the Start condition matches and the SLA will never attachPlease refer to the documentation for details: https://docs.servicenow.com/csh?topicname=c_SLAConditions.html&version=latestSection on "SLA condition evaluation"