Background job "Update Task to Items" has many instances in Queued state.Issue The background job 'Update Task to Items' has a large backlog and is unable to catch up. Jobs are running, but taking a long time to complete causing the jobs to be queued for many days.SymptomsQuerying the background jobs and grouping by state, one can see a few jobs in processing state, while a large number in Queued state. ReleaseAllCauseThese jobs are slow because the remediation tasks processed as part of the background job 'Update Task to Items' contain a large number of VITs. The concurrency for this job is approximately 4. Hence, if a large number of RTs are updated with only comments, multiple jobs will be queued.We advise customers to disable these two OOB BRs to prevent cascading comments and work note updates from the RT to VIT. This would reduce the number of background jobs. There isn't much we can do to speed this up because it is expected when remediation tasks have a large number of associated closed VITs.https://<instance>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=d24d761fb7331300e8f98a11ee11a905https://<instance>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=1ce06e629f13120034c6b6a0942e7073ResolutionDisable the two OOB BRs to prevent cascading comments and work note updates from the RT to VIT, which would reduce the number of background jobs. Consider closing and/or killing all the 'Task to Item Update' background jobs (sn_sec_cmn_background_job).