Service Level Agreements (SLA) attached twice to catalog taskIssue Task Service Level Agreements (SLA) gets attached again even when one is already presentCauseThis is a race condition issue. Notice the below findings:On TASKXXXXXX checking the auditUpdate happen on 20:12:59 has an internal checkpoint as "16a2c807d610000001" but the update number is same as "1" Update happen on 20:13:23 has an internal checkpoint as "16a2c80dc1f0000001"but the update number is same as "1" In this situation, a race condition has occurred. After the update occurs, the system still possesses information that the stop condition was not satisfied, but the start condition was, so it reattaches once more.ResolutionInsert a timer between the "run script" activity in the workflow to pause the transaction and then monitor whether or not this solves the problemRelated LinksKB0719833-Duplicate SLA getting attached when state of Incident was Resolved KB0855438-Duplicate SLA's are getting attached to Incident