CI mismatchedIssue Question:After correcting CI Lookup Rules and updating the sn_sec_cmn_ignoreCIClass system property some VIT's are still using old CI's (which now should not be used as they are in the ignoreCIClass)Ex: SDI000000001192 - this DI was updated to use a new CI based on reapplication of lookup rules, but VIT0222039I which is associated is using a class that should be ignored by the lookup rule (VMware Virtual Machine Instance).Answer:This is the way the application is designed to work. Have a look into the 'Handle Configuration item change' business rule and methods use by the script. Closed DET/VITs will not have their CI changed even if the CI gets changed on the discovered item during the CI lookup rules reapply. The logic which evaluated this is in _processVIWithDetections function of CIChangeProcessorBase script include.Business Rule:https://<instance_name>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=e6f5132053711010db5eddeeff7b1248