{"version":"2.1.280","anchor":"session-scoped-bypass-added-to-fable-overage-consent-check","canonical_anchor":"session-scoped-bypass-added-to-fable-overage-consent-check","heading":"Session-scoped bypass added to fable overage consent check","tier":"internal","area":"Usage & Limits","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/session-scoped-bypass-added-to-fable-overage-consent-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Session-scoped bypass added to fable overage consent check\n\nA per-session cache can now short-circuit the fable overage billing consent check\n\n**Unclear.** The finding does not state why the session-scoped cache was added, only what it does.\n\n**What**\n\nThe function that checks whether a user has consented to fable overage billing now first checks a cached value scoped to the current session. If that cached value matches the current organization and account, it short-circuits to \"consented\" without checking the persisted `fableOverageConsentV2` record.\n\n**Why**\n\nThis likely avoids repeatedly re-checking the persisted consent record within the same session, though the finding doesn't specify the performance or behavioral benefit directly.\n\n- Area: Usage & Limits\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}