Discovered items match to Unmatched CI instead of the correct CI recordIssue When reapply CI lookup rules in Vulnerability Response, discovered items fail to match to their intended CI and default to an Unmatched CI record. Symptoms The following behaviors occur when CI lookup rules are applied to discovered items: Discovered items do not match to the correct CI in the CMDB.Discovered items match to the Unmatched CI placeholder record instead.Reapplying CI lookup rules does not resolve the mismatch.The CI lookup background job completes successfully but reports zero items matched. Facts The following environment details are relevant to this issue: Product: Vulnerability Response with <scanner> integration.Tables affected: sn_sec_cmn_src_ci (discovered items), cmdb_ciCustom CI lookup rules are defined and active on the affected instance.One or more custom business rules exist on the cmdb_ci tablesThe background job that executes CI lookup rules runs under the SecCommon.System user account.System property to ignore certain CI class doesn't have the name of intended CI class. Release This issue is not specific to any release. Cause 1. A custom query Business Rule was running on cmdb_ci table and its extended tables (including cmdb_ci_server class) imposed security restrictions, preventing the CI lookup job from accessing or matching the correct CMDB record. 2. The Business Rule caused errors during the lookup process, particularly when the script attempted to access records in the cmdb_ci_server table, leading to skipped class-switch handling in IRE. Resolution 1. Identify Business rule by checking transaction in logs for background job run.2. Disabling the custom Business Rule.2. Reapply the CI lookup rule on the affected discovered item to ensure the correct CI is matched after the Business Rule is disabled. 3. Verify that the 'SecCommon.System' user, which runs the scheduled job for the CI lookup rule, has appropriate access permissions to avoid conflicts with the Business Rule. 4. Re-enable the custom Business Rule after confirming the lookup rule functions correctly, and monitor for recurrence. Related Links CI Lookup Rules in Vulnerability Response — https://support.servicenow.com/kb/kb?id=kb_article_view&sysparm_article=KB1625015Business Rules scripting reference — https://www.servicenow.com/docs/bundle/zurich-api-reference/page/script/business-rules/concept/c_BusinessRules.htmlRapid7 InsightVM integration configuration — https://www.servicenow.com/docs/r/security-management/vulnerability-response/r7-setup-ivm.htmlCMDB table hierarchy and extension — https://www.servicenow.com/docs/bundle/zurich-platform-administration/page/administer/table-administration/concept/table-extension-and-classes.htmlCI Matching Community Article — https://www.servicenow.com/community/secops-articles/servicenow-vulnerability-response-ci-matching-tuning/ta-p/2315460