---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# SLO creator agent system properties

# SLO creator agent system properties {#ariaid-title1}

Release version: Australia  
Updated August 19, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure how the SLO creator agent generates and activates SLOs.
To turn automatic SLO generation on or off and manage email notifications for generated SLOs, see [Manage SLO creator agent settings](https://www.servicenow.com/docs/dN0l25C9IjtJrqN50o2Y6Q "Activate or deactivate the service level objective (SLO) creator agent and configure the notification settings.").  
Note:  
Property changes apply only to newly generated SLOs. Existing SLOs aren't recalculated.

## `sn_ai_agents_slo.commitment_buffer` {#slo-creator-agent-system-properties__section_commitment-buffer}

Description
:   Adds a buffer to an availability commitment when the agent calculates the SLO
    target. Applies only when the agent finds an availability commitment.

Values
:   Default: `0.09`

When to adjust
:   Increase the buffer to set stricter SLO targets and provide earlier warning
    before the service falls below its availability commitment. Decrease it if the
    generated targets are too strict.

## `sn_ai_agents_slo.create_slo_mode` {#slo-creator-agent-system-properties__section_create-slo-mode}

Description
:   Controls if the agent activates generated SLOs automatically or saves them as
    drafts.

Values
:   Default: `auto_activate`

    Other value:
    `draft`

When to adjust
:   Use `draft` to review and edit generated SLOs before
    activation. Use `auto_activate` when generated SLOs can take
    effect without review. Error budget notifications begin after activation.

## `sn_ai_agents_slo.linked_alerts_cap` {#slo-creator-agent-system-properties__section_linked-alerts-cap}

Description
:   Limits the number of critical alerts associated with an incident that the agent considers when generating SLOs.

Values
:   Default: `5`

    Maximum: `10`

When to adjust
:   Increase the value when incidents commonly produce more relevant critical
    alerts than the default includes. Decrease it when numerous alerts represent
    the same underlying issue.

## `sn_ai_agents_slo.linked_outages_cap` {#slo-creator-agent-system-properties__section_linked-outages-cap}

Description
:   Limits the number of outages associated with an incident that the agent considers when generating SLOs.

Values
:   Default: `5`

    Maximum: `10`

When to adjust
:   Increase the value when a single incident commonly spans more outage records
    than the default includes. Decrease it when multiple outage records represent
    the same underlying issue.

## `sn_ai_agents_slo.orphan_alert_window_days` {#slo-creator-agent-system-properties__section_orphan-alert-window-days}

Description
:   Specifies how far back the agent looks for critical alerts that aren't associated with an incident when generating SLOs.

Values
:   Default: `30`

    Range: `7-90`

When to adjust
:   Use a shorter window when older alerts no longer reflect current service
    reliability. Use a longer window to account for less frequent or recurring
    alert patterns.

## `sn_ai_agents_slo.other_incident_window_days` {#slo-creator-agent-system-properties__section_other-incident-window-days}

Description
:   Specifies how far back the agent looks for other P1 and P2 incidents associated with the service or CI when generating SLOs.

Values
:   Default: `90`

    Range: `30-180`

When to adjust
:   Use a shorter window to focus on recent conditions. Use a longer window to
    account for severe incidents that occur less frequently.