Not switched on
Useful1 Signal3
Five analytics events cover the weekly limit-reset flow.
Nothing fires unless tengu_nifty_lemur is enabled, off here.
What's wrong with this entry?
Anonymous. No account, no email.
What
The limit-reset flow reports the eligibility check, hitting the limit, the notice being shown, your selection and the claim result. Nothing fires unless the feature is enabled by tengu_nifty_lemur, which is off by default here.
Details
- Each event carries the experiment arm, subscription tier, availability, low-priority state, config version and the server-supplied tenure, billing path, billing period and extra usage buckets.
Evidence
tengu_juniper_tide_wall
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