Change Enablement - Discrepency between, Conflict last run field VS Conflicts Tab / Last checked

[Nitram]

Is this a Known issue? Is this Out of the Box? 
Anyone else is getting this discrepency?

[Dr Atul G- LNG]

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.

[Nitram · Accepted solution]

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>.

[Dr Atul G- LNG]

yes mate as per design only. 

[Dr Atul G- LNG]

Hi @Nitram 

You should my answer as solution mate, as I supported you on the query.