{"version":"2.1.248","anchor":"two-new-usage-limit-notices-registered-at-session-start","canonical_anchor":"two-new-usage-limit-notices-registered-at-session-start","heading":"Two new usage-limit notices registered at session start","tier":"soon","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/two-new-usage-limit-notices-registered-at-session-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Two new usage-limit notices registered at session start\n\nTwo new usage-limit notices are registered, tied to menu rows behind an off gate.\n\n**What**\n\nSession start registers two new usage-limit notice ids, one high priority and one medium, matching the new actionable and already-spent rows in the usage-limit menu. Their labels are looked up at runtime, so the source does not spell out the offer. No named flag sits on the registration itself, though the surrounding menu reads a separate gate that defaults to false.\n\n**Evidence**\n\n`juniper-tide-spent`\n\n- Area: Usage & Limits\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}