So we found earlier this week all of our policy scan broke after we upgraded to 7.3.2. We noticed that if scanned with “old” templates, there would be no results for any assets. We discovered that if you modify a policy by just adding a space or some random text, it forced the policy to be updated to a 7.3.2 policy template and you could then scan successfully with the policies. Support was made aware of this issue, they don’t have an immediate fix, but if you’re needing policy scans done this should get you going.