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.
SLA Timeline issue - Keep history - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • SLA Timeline issue - Keep history
KB0818385

SLA Timeline issue - Keep history


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

Issue


You have reported an issue whereby you are noticed an issue in the SLA Timeline after upgrading the SNOW COVEA instance .
The SLAs which are "out of time" appear in red from the start, and they were green, then orange, then red, depending on the different thresholds crossed (see attachment).
You request to keep the history of SLA incident states/color according to the states by which it happened.

Cause

Customer had several modified script includes which were impacting this behavior.

2 copies of task sla:
https://xxxx.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=10d0c7590a0a2c394e2b1766a6e5fbad inactive OOB

https://xxxx.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=73d6bfb1db064780fc93f9c41d96193b active

2 copies of SLACalculatorNG
https://coveadev.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=9ba81e3d0a0a2c513f0ea765abd97c40 inactive OOB

https://coveadev.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=a9303eb7db06878096c0f3d31d961922 active

 

Customer had inactivated the OOB script and was using Customized files.

Resolution



Issue was resolved after merging with OOB.

They have modified these customized files to include the OOB code that has been missed out while still keeping their customizations.
This has now resolved the issue.



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.