the issue here is that the cache loading was sped up by tweaking how much data was loaded as well as the number of roundtrips required to pull that data into the cache. as a result, AlertCondition had two fields marked as lazy, which were previously marked as eager. i missed this during my initial testing, because i was focusing on the performance bottleneck at the time: measurement-based alerts. and our smoke testing missed this too.