Duplicate SLA getting attached when state of Incident was ResolvedIssue Task SLA - service level agreement (Resolution) attached second time even after Incident state is Resolved. ReleaseOrlando, QuebecCauseUpon reviewing SLA definition found following Start Condition: Assignment group.Company- is - ABCAssignment group.Parent - is - ServerAssignment group.Parent - contains - Storage However, there is NO state condition mentioned in Start condition. Hence. when the incident is Resolved, SLA Engine is again checking start condition which are matching and attaching SLA twice.ResolutionIn SLA definition start condition add one more condition: State - is not one of - Closed or Resolved.