Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Difference in timings in two task SLAs on the same task running off of the same SLA conditions - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Difference in timings in two task SLAs on the same task running off of the same SLA conditions
KB0852579

Difference in timings in two task SLAs on the same task running off of the same SLA conditions


1079 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

The user was seeing timing discrepancies when comparing two task SLAs, based on two separate and distinct SLA Definitions which had the same conditions within each SLA Definition respectively. They wanted to know why the timings weren't identical.

Resolution

The issue, in this case, is that while the SLA Start, Pause, Stop, and Reset conditions were the same, the Schedule was not. 

On one Schedule for one SLA Definition, the "Time zone" was set to "Floating", and on another, the "Time zone" was set to "US/Central".

This very small difference is what caused the issue. 

If a user selects the value of "Floating" for their Time Zone schedule field, the time zone is relative to whatever process is accessing the item at the time.

For example, if a resource manager in Amsterdam sets a floating schedule for 8:00 AM. to 5:00 PM, a user in San Jose sees the schedule as 8:00 AM to 5:00 PM.

When a schedule is defined in a specific time zone however, like US/Central, users in different time zones see the schedule with their own time zone applied. This is the difference and the cause of the behavior.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.