Corrupt usage-stats cache is repaired or rebuilt instead of showing you garbage numbers.
What's wrong with this entry?
The cached usage-stats aggregate is normalised defensively on load, and falls back to a full rescan when it cannot be repaired.
- Non-finite numbers are coerced to 0.
__proto__model keys are dropped.- Dates must survive a strict
YYYY-MM-DDround-trip to be accepted. - If no usable date can be recovered, aggregates are reset for a full rescan and a debug line is emitted.
resetting aggregates for a full rescan
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Extra-usage panel now shows for team and enterprise accounts
Both mention usage limit
-
v2.1.236
Wrap-up hint near the usage limit is now per-plan and once per window
Both mention usage limit
-
v2.1.236
Visible notice when approaching the 5-hour usage limit
Both mention usage limit