Process Vulnerability Solution Metrics Queue - Chained Solutions & Non-chained in Australia Release

[Jay_N]

In the Yokohama release,  vulnerability solutions management had one schedule job (Process Vulnerability Solution Metrics Queue)

When I upgraded to Australia, I see they have broken down the scheduled jobs Process Vulnerability Solution Metrics Queue into two jobs:

1. Process Vulnerability Solution Metrics Queue - Chained Solutions
2. Process Vulnerability Solution Metrics Queue - Non-chained Solutions.

I would like to know what changes are in the script and what are the impact. I checked the updated docs for vulnerability management for Australia but it only mentions the scheduled job Process Vulnerability Solution Metrics Queue .

[william_tran · Accepted solution]

Hi Jay_N, 

The documentation page was updated about a week ago with the new updates. Please see below for the updates. 

Split Processing Jobs (v26.5.3+)

Beginning with v26.5.3, the scheduled job was split into two parallel jobs to support concurrent processing:

• Chained Solutions Job: Handles MSRC solutions. MSRC publishes monthly incremental updates structured as supersedence chains. Each solution supersedes one or more prior ones. This job performs a directed graph traversal to identify the highest-superseding solution, then designates it as the preferred solution. Note: graph traversal is complex and may require significant processing time in large environments.
• Non-Chained Solutions Job: Handles Red Hat and all other integrations. These sources don't use supersedence chain relationships and don't require graph-based resolution. They are processed via a faster, streamlined execution path.

I hope this helps!

William