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.
Invalid Date error after running a 'Check Conflicts' on a change request for a user who has date format set to anything other than system format - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Invalid Date error after running a 'Check Conflicts' on a change request for a user who has date format set to anything other than system format
KB0636092

Invalid Date error after running a 'Check Conflicts' on a change request for a user who has date format set to anything other than system format


3024 Views Last updated : Oct 16, 2023 public Copy Permalink
KB Summary by Now Assist

Description

Saving a change request after running a check conflicts causes error Invalid date on Conflict last run field. This happens for a user for who the date format is set to anything other than system date format.

Steps to Reproduce

 

On a Jakarta OOB instance version glide-jakarta-05-03-2017__patch0-05-18-2017

  1. Set current user profile Date Format to anything other than system format. For example, as an ITIL user set the date format as dd-mm-yyyy
  2. On a Change Request, set Planned Dates that generate a conflict, then Save record. This works correctly as expected.
  3. After reload, navigate to Conflicts tab, and click on Check Conflicts
  4. This changes the field Conflicts last run date time value.
  5. Save the change record.

Result: Invalid date error appears under Conflicts last run date time field.

 

Workaround

This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In field to determine whether any versions have a permanent fix.


Related Problem: PRB1083532

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.