sys_updated_on field not updated on CI discoveryIssue After a successful pattern discovery, the last_discovered (Most recent discovery) field is updated and the sys_updated_on is not.ReleasePre New York Patch 7.CauseIn a pattern discovery, if the data collected is identical to what the CI already had the CI will not be changed. However, the last_discovered field still needs to be updated to represent the last time the CI was discovered. Pattern discovery can batch update the last_discovered field on a CI. No business rules are called when the last_discovered field is updated via batch, a direct DB update is done to the last_discovered field.ResolutionPre New York Patch 7: The system property glide.identification_engine.batch_update_last_discovered controls whether last_discovered field is batch updated or not. The default value is true. Discovery will do a standard GlideRecord update to the last_discovered field when glide.identification_engine.batch_update_last_discovered = false, and therefore also update the sys_updated_on field. New York Patch 7+: This behavior changed and the sys_updated_on field will be updated as well when last_discovered is updated.Related Linkshttps://docs.servicenow.com/csh?topicname=properties-id-reconciliation.html&version=latest