Vulnerability Response - Vulnerability Calculator: Reapply Calculator doing nothing?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2022 10:54 AM
Hi -
We've recently implemented Vulnerability Response in our instance. I've just been asked to update the vulnerability calculators so that the risk is set based on Vulnerability Score V3 instead of the source Severity. I have done so, and going to a Vulnerable Item, right clicking on the top nav bar, and selecting "Calculate Risk Score" is now updating the risk score to the desired value.
However, this is just fixing 1 VIT record, and not the many, many active VIT records that exist.
I have gone to the active Vulnerability Calculator and clicked on the "Reapply Calculator" UI Action. It warns that it may take a long time to rerun it on all VITs, and that's fine... The problem is it's not starting!
It's been hours, and not a single VIT record has had their risk updated. Is it only run once per day? Can I go to a scheduled job and run it on demand given that I'm trying to test this on our dev instance? Might the job be stuck and need to be killed so it can restart?
Any assistance appreciated! I'm not going to be able to fix these once at a time.
Thanks!
- Labels:
-
Integrations
-
Scripting and Coding

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2022 11:48 PM
Hello Rita,
I believe you are doing right thing by going in to the "Vulnerability calculator" and click on the UI action "Reapply calculator", As message says "This action updates all active vulnerable item (VI) risk scores in the background. Depending on how many VIs you have, this can take a long time." , It should be completed in some time depends on your vulnerable items record? Can you please check if its completed.
If not, You can go to the "Progress worker" or "Active transactions" and see if the background job is running or stuck at some node due to long processes running on the node.
you may need to click on the UI action again in the off hours that may increase the processing. Hope it helps.
Please Mark ✅ Correct/helpful, if applicable, Thanks!!
Regards
Sulabh Garg
Regards
Sulabh Garg

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2022 02:01 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2022 11:16 AM
Both had been failing to run, but it appears as though the issue was actually because there was a huge backlog in scheduled jobs due to one of our integration partners testing a new server and sending our dev system enough tickets to create a huge backlog.
We have cleared those out, and I was actually able to get this working.
Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2022 10:16 PM
Hi Rita,
I am glad it started working, If my answers help you in anyway, can you please mark it correct & helpful. Thanks
Regards
Sulabh Garg