- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2025 07:45 AM
Is this a Known issue? Is this Out of the Box?
Anyone else is getting this discrepency?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2025 05:20 AM
Thanks for the confirmation mate.. So this is Working as Designed ! :-1
ServiceNOW should rename the field to be <Conflict First Run> instead of <Conflict Last Run>.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2025 11:07 PM
Hi @Nitram
This isn’t a bug—it seems like expected behavior, at least from what I’ve observed.
The "Last Check" will only be updated and synced with the most recent run when you manually click the "Check Conflict" UI action under the Conflict tab.
I tested this in my PDI, and it’s populating both dates the same way, so it appears to require manual intervention by clicking the UI action.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2025 05:20 AM
Thanks for the confirmation mate.. So this is Working as Designed ! :-1
ServiceNOW should rename the field to be <Conflict First Run> instead of <Conflict Last Run>.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2025 06:50 AM
yes mate as per design only.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2025 07:30 AM