Hi @devika,
No, an empty Normalization Suggestions table does not by itself mean that normalization is failing.
Match Not Found means the discovery model has not been fully normalized. Such discovery models can be manually normalized or normalized using the available Content Service rules.
Normalization Suggestions are specifically generated for manually normalized discovery models during the weekly normalization process. Therefore, if the affected discovery models have not been manually normalized, you should not expect corresponding records in the Normalization Suggestions table.
So, in this case, Match Not Found + no Normalization Suggestion records is not necessarily an issue with the normalization job.
You can manually normalize the affected Discovery Model from
Software Asset Workspace → License operations → Discovery models → select the model → ⋯ → Normalize.
Match Not Found → discovery model is not fully normalized.
No Normalization Suggestion → expected if it hasn't gone through the manual-normalization/suggestion process.
