{"version":"2.1.304","anchor":"policy-limits-cache-restamp-keeps-original-confirmedat-under","canonical_anchor":"policy-limits-cache-restamp-keeps-original-confirmedat-under","heading":"Cached organisation limits can now expire instead of being refreshed forever","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/policy-limits-cache-restamp-keeps-original-confirmedat-under","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Cached organisation limits can now expire instead of being refreshed forever\n\nWhen cached organisation limits are re-confirmed, Claude Code may now keep the original confirmation time instead of resetting it\n\n**Unclear.** The condition under which the original time is kept is not identified.\n\n**What**\n\nClaude Code keeps a saved copy of the limits an organisation sets. When it re-confirms that copy, it used to stamp it with the current time. Under one condition it now keeps the original confirmation time instead. Claude Code also removes an unstamped copy that the current login cannot re-confirm once the server has replaced it.\n\n**Why**\n\nA saved copy of the limits can now age and expire rather than being kept fresh indefinitely.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}