Overview:

Currently, Scanner v4 vulnerability data update workflow errors out if one or more updaters fail or any other error occurs.

We want the update workflow to continue running even if some updaters fail, although the generated data bundle might be incomplete.

We also want to examine how the ACS tracks the timestamp of updates per data source (should be tracked in DB), so ACS is aware that some data might be outdated.

Do UI gets involved in to indicate update status per data source? Possibly, but that will require discussion between Scanner team and the UI team.