The Rapid7 Integration generates duplicate VITs for same CI and vulnerability SummaryBACKGROUND: This article would be looking at an issue, where the customer may see some duplicated Vulnerable Items (VITs), when upgrading from version before 9 to 10 onwards. Multi-instances for Rapid7 IVM did not exist before version 9. Therefore the field, integration instance, was not populated for the existing Vulnerability Items, before an upgrade. When data from detections are imported, the "Rapid7 Vulnerable Item Integration - API" integration checks for any existing Vulnerable items based on external id and integration instance. Since the integration instance is not populated for older VITs, these VITs are skipped when querying with integration instance and external id. As a result, duplicate VITs are created with the same external id. InstructionsRESOLUTION: If the duplicate VITs have been created, then the newly created ones may have to be deleted before running the provided script.This fix script would add the integration instance for the VIs for which integration instance is not defined due to upgrade. Once, this is done, customer can re-trigger "Rapid7 Vulnerable Item Integration - API" integration. This integration checks for the existing VITs and does not create duplicates. Run the fix script mentioned below to resolve the issue mentioned above : var gr = new GlideRecord("sn_vul_vulnerable_item");gr.addEncodedQuery("integration_instanceISEMPTY^source=Rapid7");gr.query();gr.setValue("integration_instance", "f521564b77c23300ac0a7c5168106100");gr.setValue("integration", "4b209a0b77c23300ac0a7c51681061fb");gr.updateMultiple();