Security Background Jobs Remaining in Queued State after migration to USEMIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } After migrating from Vulnerability Response to Unified Security Exposure Management (USEM), administrators may observe security background jobs remaining in a Queued state and not completing processing. This can prevent remediation tasks from being created, risk score calculations from updating, and rollup processing from completing successfully. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Symptoms USEM scheduled jobs remain in a Queued state for an extended period.Remediation tasks are not generated as expected.Risk score calculations or vulnerability prioritization updates do not complete.Rollup calculations do not complete.Security workflow automation appears stalled even though jobs are scheduled. Facts<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Affected Tables The issue has been observed on the following USEM configuration tables: Configuration Type USEM Table Vulnerability Assignment Rule sn_sec_wf_assign_rule Remediation Target Rule sn_sec_wf_ttr_rule Vulnerability Rollup Configuration sn_sec_wf_rollup_config Remediation Task Rule sn_sec_rem_task_rule Exception Rule sn_sec_exception_rule Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } N/A Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The Applies To field, stored as applies_to, is blank on one or more USEM configuration tables. Security background jobs rely on this value to determine the applicable execution scope. If the field is empty, the platform cannot determine which configurations should be processed, which can cause related background jobs to remain queued. This condition can occur during migration when records are created in the new USEM tables without copying the corresponding applies_to value from the legacy Vulnerability Response tables. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Populate the missing applies_to values on the USEM tables by copying the value from the corresponding legacy Vulnerability Response table. The remediation script below updates records in the target USEM table only where applies_to is empty. (You can modify the script according to your needs) Important Validate that the legacy source table contains the correct applies_to value before running the script. Review the output logs after each execution and confirm the affected USEM table has no remaining records with an empty applies_to value. Remediation Procedure Navigate to System Diagnostics > Scripts - Background.Select one migration pair from the Migration Mapping table.Update the oldTable and newTable variables in the script.Execute the script.Repeat the process for each affected table pair.Verify that the applies_to field is populated on each target USEM table.Re-run the affected USEM background jobs and validate processing resumes normally. Remediation Script Copy applies_to from a deprecated Vulnerability Response table to the corresponding USEM table // Copy applies_to from deprecated table to new USEM table// Example: Copy from old sn_vul_assignment_rule to new sn_sec_wf_assign_rulevar oldTable = 'sn_vul_assignment_rule'; // Deprecated tablevar newTable = 'sn_sec_wf_assign_rule'; // New USEM table// Get applies_to from deprecated tablevar oldGr = new GlideRecord(oldTable);oldGr.setLimit(1);oldGr.query();if (oldGr.next() && oldGr.applies_to) { var appliesTo = oldGr.applies_to.toString(); // Update all empty applies_to values in new table var newGr = new GlideRecord(newTable); newGr.addQuery('applies_to', 'ISEMPTY'); newGr.query(); var count = 0; while (newGr.next()) { newGr.applies_to = appliesTo; newGr.update(); count++; } gs.log('Updated ' + count + ' records in ' + newTable, 'USEM Migration');} else { gs.log('ERROR: No applies_to found in ' + oldTable, 'USEM Migration');} Migration Mapping Run the script once for each table pair listed below: Legacy Vulnerability Response Table New USEM Table sn_vul_assignment_rule sn_sec_wf_assign_rule sn_vul_ttr_rule sn_sec_wf_ttr_rule sn_vul_rollup sn_sec_wf_rollup_config sn_vul_grouping_rule sn_sec_rem_task_rule sn_vul_auto_exception_rule sn_sec_exception_rule Verification Run the following validation script against each USEM table to confirm that no records remain with an empty applies_to value. Update the table name before running the script against the next USEM table. var gr = new GlideRecord('sn_sec_wf_assign_rule');gr.addQuery('applies_to', 'ISEMPTY');gr.query();gs.info('Empty applies_to records: ' + gr.getRowCount()); Expected result: Empty applies_to records: 0 Validation After Fix Confirm all affected USEM tables contain populated applies_to values.Re-run the affected scheduled jobs.Confirm jobs move from Queued to Completed.Confirm remediation tasks are being generated as expected.Confirm risk calculations and rollup processing complete successfully. Prevention Validate migration mappings before production deployment.Confirm required fields are copied during migration activities.Perform post-migration audits on USEM configuration tables.Verify populated applies_to values before enabling scheduled processing.Monitor USEM scheduled jobs immediately following migration.Document migration dependencies and validation procedures. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Migration Guidance to Unified Security Exposure Management https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2556844