SLA duration types

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of SLA duration types

    ServiceNow offers two SLA duration types to define the time within which a task must be completed before the SLA is breached:User specified durationandRelative duration. These durations work in conjunction with an SLA schedule if one is defined, helping you manage SLA breach times precisely according to your business needs.

    Show full answer Show less

    User specified duration

    This option allows you to set a static duration period (e.g., 8 hours) combined with a business schedule. You specify the length of time in days, hours, minutes, and seconds that the SLA must run before it is considered breached. The system converts days into 24-hour blocks and provides an example breach time on the SLA form to help you understand how the breach date is calculated. For instance, if you set 10 hours and no schedule is selected, the SLA breach time is exactly 10 hours from the start time.

    Relative duration

    Relative durations specify breach times using scripts relative to the task SLA start time. Examples include “Breach on Due Date,” “End of next business day,” or “Next business day by 4pm.” These durations require an end date and time in the future, and the relative breach time is calculated based on task or SLA record fields.

    Important considerations for relative durations:

    • Pause conditions are not compatible with relative durations.
    • If the Due Date field is empty or in the past, the breach time defaults to one second after the SLA start.
    • If the Due Date is outside the SLA schedule, the breach time adjusts to the next available scheduled time.
    • You can base relative durations on any target date/time field in your task record by customizing the SLA accordingly.

    Practical application for ServiceNow customers

    Choosing between user specified and relative durations enables you to tailor SLA breach calculations to your operational requirements. Use user specified durations when you want fixed time periods aligned with business hours. Opt for relative durations when breach times depend on dynamic task attributes like due dates or business day cutoffs.

    This flexibility ensures accurate SLA breach tracking, helps you meet service commitments, and supports effective SLA management within your ServiceNow environment.

    You can select one of two SLA duration types to define the length of time within which a task must be completed before the SLA is breached.

    If an SLA schedule is defined, the duration works along with the schedule. In a user-specific duration, you can choose to specify the length of time that an SLA must run before it is marked as breached. Relative durations specify durations that are relative to the start time of the task SLA and are defined using a script.

    When you define an SLA, you can select either a user specified duration or a relative duration.
    User specified duration
    Specifies a static duration period, such as 8 hours, along with a business schedule. The Duration field is displayed, enabling you to specify the length of time in days, hours, minutes, and seconds that the SLA must run before it is marked as breached. The number of days specified in the Duration field is converted to 24- hour blocks.

    Each time that you set a duration, an example breach time information message is displayed at the top of the form. This information assists you to understand how the breach date is calculated. For example, if the current date is January 1, 2015, the time is 10:30 am, and the duration is set to 10 hours and no schedule has been selected, the following information message is displayed: An SLA starting now will end breach on 2015-01-01 20:30 (Actual elapsed time: 10 Hours).

    Relative duration
    Specifies a duration relative to the start time of the task SLA and is defined using a script. Provision of an end date and time in the future is necessary to set a relative duration. For example, you can select a relative duration such as Breach on Due Date, End of next business day or Next business day by 4pm. The set of relative durations is defined in the core configuration using script-based duration calculations.
    Note:
    Pause conditions are not compatible with relative durations.
    Specify a relative duration
    To specify a relative duration, select an option such as Next business day by 4pm or End of next business day from the list of available relative durations in the Duration type field.

    When you select a relative duration such as Next business day by 4pm, the Relative duration works on field is displayed. You can use Task record or SLA record and the record you select is available as current for the relative duration script.

    The Breach on Due Date sets the breach time of the SLA to the date and time from the Due Date field of the task that the SLA is attached to.

    If no information is available in the Due Date field, or the date and time provided is in the past, the breach time of the task SLA is calculated to be one second ahead of the task SLA start time. If the date and time in the Due Date field is outside the schedule for the task SLA, the breach time is set to the next available scheduled time. For example, if the SLA definition specifies a task SLA schedule as 08:00-16:00 and the value in the Due Date field is Wednesday 11th Jan 2017 20:30, the breach time is set to Thursday 12th 2017 Jan 08:00.

    If your task record has a target date and time field, you can create an SLA with a relative duration based on that field.