Yes the computers are in scope. The logs were all populated last week. The majority of our policies so No logs for this policy. Even the ones scoped for DEP which should have at least 100 computers in there.
We're seeing this with our JSS post-upgrade (cloud hosted, us-east-1) - the device records are showing new policy activity in history, but all existing policy logs now show no activity. We have a support case open. Interestingly, a newly created policy behaves as expected, logging in both the device policy history and in the policy log. This does not appear to be a client-facing issue - Self Service works fine and policies ARE executing successfully.
Does Jamf Remote still work? That's another disconnect we're seeing - Jamf Remote thinks that the JSS is not valid.
Currently awaiting feedback from Cloud Operations.
HQ came back with reference to two specific device records and instructions to click Edit, then Save in the User & Location for each record - no clue on the root cause, but doing that procedural dance restored everything to normal.
Open up a support case and let them know you're seeing the issue - you should hopefully find a similarly quick resolution.
I'm having this same problem with an on-prem installation of 10.20.1, and I hope it's responsible for a few other disruptive bugs we're noticing as well. The dashboard that appears after logging into my account only shows one policy before an indefinite spinning progress bar appears, and similarly, I've also had a couple policies not even load. Saving a computer group also displays "An error occurred while saving the changes."
Seeing the same issues here. Standard Cloud 10.20.1 (Began after the upgrade to 10.20.1). I'm also seeing the dashboard issue described by @jhamil50 above - if any policy is added to the dashboard, the whole page just spins forever. If I remove all policies from the Dashboard, it displays Smart Groups and Patch Reporting without issue.
Worked with Jamf as we were seeing this as well, and found that it was due to 2 computers in our fleet that were assigned to invalid user objects. If you are seeing this and are not on Jamf 10.21 yet, it might be related to PI-008061. Jamf gave us a MySQL command to check which machines are assigned to invalid users, and repairing those 2 computer records resolved it.
Same thing happened to us after upgrading our on-prem instance to 10.20.1, strangely it was also 2 computers that were assigned to invalid user objects after running the MySQL command from Jamf Support.