Product showing non-compliant when all versions are compliant

[Anshul Dewan]

Hi Community,

We are seeing a discrepancy in SAM Pro compliance status. In several cases, all versions under a product are marked Compliant, but the product itself shows Not compliant, and the publisher shows 0% Compliant.

The attached are a few examples that demonstrates the behavior.

Does anyone know how SAM Pro determines or rolls up compliance status from the version level to the product and publisher levels, and what could cause these statuses to differ?