Vulnerability Response Integrations May Create Empty Import SetsSummarySome of the out-of-box Vulnerability Response integrations may create empty Import Sets. These Import Sets may have an associated Import Set Run record that's in State 'Completed with errors'. The Import Set itself will have an error message similar to this (which just indicates the Import Set Run failed as no data was in the Import Set): Loading import set table with error: sn_vul_msrc_solution_import (sn_vul_msrc_solution_import is the import staging table for Microsoft Security Response Center Solution, different integrations will have different import staging tables) This issue could affect Vulnerability Response (VR) integrations, such as: Microsoft Security Response Center SolutionTenable integrationMicrosoft Threat and Vulnerability Management (MS TVM) integrationAny other Vulnerability Response (VR) integration Our developers have confirmed that this is the intended behaviour for when there's no updated/fresh data for the integrations to import. The suggestion is that the Import Set errors and Import Set Runs with State 'Completed with errors' should be ignored. Instead of looking at the Import Sets, the success or failure of VR integrations should be monitored using the State and Substate fields on Vulnerability Integration Runs[sn_vul_integration_run] records.Related LinksMSRC Specific Info These empty Import Sets can happen with the Microsoft Security Response Center Solution when it calls the 'updates' API, https://api.msrc.microsoft.com/updates?api-version=2018, is to see if any bulletin needs refreshing. For each item returned from that MSRC API endpoint it will compare with the records in the table sn_vul_msrc_update and see if any bulletin needs refreshing based on the release date time. If none of the bulletins needs to be refreshed then it's intended behaviour that an empty Import Set is created.