Vulnerability Response job "Process Vulnerability Solution Metrics Queue" taking days to complete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2025 11:42 AM
Hey everyone,
We have vulnerability response setup with multiple integrations. After setting up our most recent integrations "Tenable" and "Microsoft TVM" I am seeing a job that is running for days. The job name is "Process Vulnerability Solution Metrics Queue". When I cancel it, it starts back up. Does anyone have any knowledge on how long this should be taking to complete or timeout? Where should I check for issues with this job?
I have not been able to find much on this in my searches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2025 11:41 AM - edited 03-07-2025 11:41 AM
will do. Thank ya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2025 08:07 AM
Hi @dan167 , Is there any update to this? Did the ServiceNow support help you reduce the run time of the job? I am stuck with similar issue and job is running for more than 2 days now. My configurations are similar to yours -
1. VR application version - 25.0.7
2. The system property sn_vul.populate_scanner_solutions is set to false
3. Handling roughly around 1M VITs
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2025 08:19 AM
They opened have a problem ticket opened on this issue PRB1807050. SN said that the job taking a long time to complete is a known issue and they will be trying to improve the feature in a future VR release. Date TBD.
For me the job does complete at some time but takes multiple days. Right now, the transaction has been running for almost 3 days.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2025 08:37 AM
Thank you so much for the quick response! Hope one of the future releases take care of this!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-19-2025 05:04 AM
Hi Dan,
Does the instance use domain separation? If so, it might be because the job created in a domain might not have the 'Run as' user from the same domain. Let me know if that's the issue.