Task Service Level Agreement (SLAs) are not createdIssue When an incident is created, the corresponding Task Service Level Agreement (SLAs) are not createdCause'com.snc.sls.engine.async' system property is enabled, so the Task Service Level Agreement (SLAs) will be created asynchronously.When an incident is created, a new record is created in Service Level Agreement (SLA) Async Queue [sla_async_queue] table which is then picked up by the 'SLA Async Delegator' scheduled job (runs every 5 seconds) which then creates a Task Service Level Agreement (SLA) recordSo if all the schedule workers are busy, then this scheduled job will have to wait for one of the workers to free up, which will cause a delay in Task Service Level Agreement (SLA) creationResolutionThere is no issue with Task Service Level Agreement (SLA) creation. Once, a scheduled worker becomes free, the 'SLA Async Delegator' scheduled job will run and create the task Service Level Agreement (SLAs). If you notice any slowness in Task Service Level Agreement (SLA) creation, check if all the scheduled workers are busy and review/kill any long-running job.The default Service Level Agreement (SLA) async job limit is 4 (defined in 'SLAAsyncDelegatorSNC' script include).If Service Level Agreement (SLA) async queue processing is still slow even after killing the long-running jobs and freeing up the scheduled workers, then create a new system property 'com.snc.sla.async.job.limit' and set the value as 8. This will make the 'SLA Async Delegator' scheduled job to create 8 new "sys_trigger" records to process the records in 'sla_async_queue' table instead of 4. This will decrease the processing time.Related LinksKB0598456: Service Level Agreements (SLA) — FAQs