"Zero observations" for user with one observation

[pisum]

digging in too much without proper access to the database to do some querying is probably a super inefficient task. i wonder if there’s a way to trigger the system to recount the observations for users whose last activity was between, say, April and June 2018? that might fix many of the problems, even if no one has the time / resources to do a proper root cause analysis.