Background Jobs Queued

[Dommer]

Hello,

We recently upgraded Vulnerability Response to version 4 and replaced the native Tenable integrations with the Service-Now Tenable Vulnerability integration. Starting fresh with no remediation tasks, when reapplying the remediation tasks rules, the background job tasks queue up and never run in production. We followed the same upgrade procedures in our DEV and TEST environments and are running with no issues. Is there anything we could check to see what could be causing these background jobs to queue up? I highlighted the job below that seems to be hanging up the rest of them during the reapply group rule background task.

[ya4936]

We are facing similar issue, could you please share more insights on how you fixed the issue

[LeonardD]

Typically, these jobs are created via message queues and performed by worker nodes. Upon detecting an event, a message will be pushed to the queues while the worker nodes keep listening to and process one by one.

Chipotle Feedback

[Bashid Bepar1]

How do you kill those Jobs. They are running for the past 3 days and some got queued up. I can't delete it the usual way. Any help is appreciated.

[SanjhiS]

Hi,

Any further information on this? Facing the same issue and background job substate is showing as user cancelled but state is still showing as In progress

[KetilE]

Hi,

There is a scheduled job that should run and end any background job running for longer than an hour. You can find the scheduled job here: https://<YOUR-INSTANCE>.service-now.com/sysauto_script.do?sys_id=d1eb5182c7bb33007393ec22c7c2607a

I have had an issue before where the user that is supposed to run this job has been removed, and thereby making it impossible for the scheduled job to run and kill the background jobs. Please verify that the user is still there and you are able to execute the scheduled job.