Follow-up from "Order vulnerabilities update by id to prevent ingestion deadlocks"

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Label this issue
• Close this issue

The following discussion from !241260 (merged) should be addressed:

• @srushik started a discussion: (+1 comment)

  I have a question regarding this -

  Advisory-driven Continuous Vulnerability Scanning and pipeline security-report ingestion run this same ingestion slice

  If this is the case, shouldn't all ingestion tasks be run with a sorted set of finding_maps? 🤔 If so can we sort all the finding maps right at the beginning of the ingestion flow? @Quintasan @ghavenga