---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Run the 2011 SLA engine asynchronously

# Run the 2011 SLA engine asynchronously {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
By default in the 2011 SLA engine, the SLA processing is performed
by the Run SLAs business rule. This business rule runs synchronously
and is the suggested configuration.

## Before you begin

Role required: sla admin, admin

## About this task

SLA processing runs asynchronously. For example, you can run this for performance reasons, such as to avoid delays when a user saves a new incident record. While the SLA engine is running asynchronously, there can be a short delay before the Task SLA records are available after updating a Task. Refresh the form to see the updated Task SLAs.

Use synchronous processing to get the best user experience. Asynchronous
processing mode is used only when there a performance issues.  
Note:  
In the 2010 engine, the Process SLAs business rule runs the asynchronous processing.

## Procedure

1. Navigate to AllService Level ManagementPropertiesSLA Engine.
2. Select Yes for the Execute the 2011 SLA Engine asynchronously (com.snc.sla.engine.async) property.
3. Click Save.

*[\>]: and then