{"version":"2.1.248","anchor":"five-analytics-events-for-the-weekly-limit-reset","canonical_anchor":"five-analytics-events-for-the-weekly-limit-reset","heading":"Five analytics events for the weekly limit reset","tier":"soon","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/five-analytics-events-for-the-weekly-limit-reset","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Five analytics events for the weekly limit reset\n\nFive analytics events cover the weekly limit-reset flow.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- 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.\n\n**Evidence**\n\n`tengu_juniper_tide_wall`\n\n- Area: Usage & Limits\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}