---
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


---

# Service Level Agreement (SLA) breakdown definitions

# Service Level Agreement (SLA) breakdown
definitions {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Using SLA breakdown, the service owner or service desk manager can see detailed task
ownership and SLA duration related data for any task SLA record associated with a task. This helps
determine which teams and users are contributing to SLA compliance.

SLA breakdown is configurable and typically should be configured for the more significant SLAs
such as P1 and P2 resolution. By default, the system deletes SLA breakdown data that is more than
one year old. This is performed by a new table cleanup job
sla_breakdown_by_assignment. Table cleanup jobs are defined in the
\[sys_auto_flush\] table.
**Related concepts**   

* [Configure Service Level Agreement (SLA)](https://servicenow-prod.fluidtopics.net/9qcEXzXJiv32S7XxKKA24w "Configure SLAs to define a set amount of time for a task to reach a certain condition, to ensure that incidents are closed or resolved according to the expectations set for customers.")