Qualys PC Results Integration Failing Silently Due to Dropped Database TableIssue The Qualys PC Results integration runs without errors but does not create or update any records because a required table no longer exists in the instance database. Symptoms Integration runs complete successfully with no failures but produces no new or updated recordsSystem logs show: GlideRecord.addQuery() - invalid table name: sn_vul_cmn_key_config Integration appears healthy but produces no output Facts The sn_vul_cmn_key_config table is required by SplitConfigurationUtil during Qualys PC Results processingIf the table does not exist, the integration silently exits without processing any resultsA table drop can be confirmed via historical database schema change records showing alter_type = drop_table against the tableA platform upgrade does not drop this table - this is caused by a manual table dropA repair installation of Vulnerability Response Common restores the table structure only and does not recover previously existing data rowsThe Key Configuration record inside the table must be restored separately from a known-good reference instanceReimporting the record from a reference instance preserves the original sys_id Release All supported releases with Qualys Vulnerability Response integration Cause The sn_vul_cmn_key_config table was dropped from the instance database, confirmed through historical schema change records. When the table is absent, SplitConfigurationUtil cannot complete its query, and the integration exits without processing results. This is not caused by a platform upgrade. Resolution Step 1: Confirm the Root Cause Navigate to the Schema Changes table on the instance using the following URL path: /<instance_url>/sys_schema_change_log_list.doAlternatively, navigate using the filter navigator: Go to All and search for Schema ChangesOr navigate directly to System Diagnostics > Schema Changes Filter the list for the affected table name: Add a filter where Table name is sn_vul_cmn_key_config Review the results and confirm an entry exists where: Alter type = drop_tableState = complete This confirms the table was manually dropped and the issue is not related to a platform upgrade Step 2: Restore the Table Navigate to System Applications > All Available Applications > AllLocate Vulnerability Response CommonSelect Repair to restore the table structure Step 3: Restore the Configuration Record Identify a known-good reference instance where the Key Configuration record exists in sn_vul_cmn_key_configExport the record from the reference instanceImport it into the affected instance to restore the original record with its sys_id intact Step 4: Verify Run Qualys PC Results once after the restoreConfirm records are created or updated as expectedComplete all steps in a non-production environment before applying to production Important Notes: A repair installation restores table structure only and does not recover data rowsA platform upgrade does not cause this table to be droppedAlways validate in non-production before applying to production