Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
What
The 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.
Why
This 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not state why the session-scoped cache was added, only what it does.
