Field Matching CI Lookup Rule Not WorkingIssue ServiceNow Vulnerability Response module is creating new configuration items (CI's) when it should not. The discovered item should have matched to the existing CI through CI lookup rules. Instead of matching the discovered item to the existing CI, VR created a new CI.CauseWhen running CI Lookup rules we have a logic to filter out decommissioned CI's and CI's that are marked as duplicate of another CI. You could confirm the logic of this filtering by looking into the 'CIIdentify' script include and the _filterCI method. As a process the method will first check if CI is marked as duplicated of another CI using "duplicate_of" column on the CI. If the CI is marked as duplicate we will fetch the CI reference in "duplicate_of" column and check if that CI's class is ignored or not and also if the CI is decommissioned or not.ResolutionFor this which displays the issue CI "duplicate_of" column is not empty and it is referencing a CI with sys id 16af90d71b8a01101f30db16ec4bcb9b. But the record is not available in the instance. If that record is available we will return that CI. VR module is not responsible for marking this CI as duplicate, this is simply a filtering method which is being used at the application level for lookup rules. CIIdentify script include:https://<instance_name>.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=45b88ff30b420300cbf38ee337673a34