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.
'Conflict Status' & 'Conflict last run' fields are not getting updated on Change record until after the record is reloaded. - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • 'Conflict Status' & 'Conflict last run' fields are not getting updated on Change record until after the record is reloaded.
KB0860312

'Conflict Status' & 'Conflict last run' fields are not getting updated on Change record until after the record is reloaded.


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

Issue

'Conflict Status' & 'Conflict last run' fields are not getting updated on Change record until after the record is reloaded.

Cause

Conflict of timing

Resolution

We confirmed that its just a timing issue and adding delay will fix this. As long as you don't have any issue with adding a bit of delay then it should be fine.

In testing, we added below code into the ChangeConflictWorker Script Include within the start method.
//adding some delay to try and fix live update not coming when the form loads.
gs.sleep(5000);

You may want to try some other method of adding this delay or make the process synchronous and the code above is just a way to demonstrate that the issue is caused by a conflict of timing and shouldn't be considered a solution unless the you decide to add that based on your own assessment of the situation.


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.