{"version":"2.1.271","anchor":"policy-limits-cache-now-tracks-the-credentials-principal-an","canonical_anchor":"policy-limits-cache-now-tracks-the-credentials-principal-an","heading":"Policy-limits cache now tracks the credential's principal and reacts to account\/login switches","tier":"internal","area":"Policy Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/policy-limits-cache-now-tracks-the-credentials-principal-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Policy-limits cache now tracks the credential's principal and reacts to account\/login switches\n\nLocal policy-limits cache now tracks which account is logged in and reacts to account switches\n\n**What**\n\nThe local cache that stores policy limits (rate-limit and compliance restrictions tied to your account) now tracks the identity, or \"principal,\" of the credential you're using. It watches for the active credential changing, for example if you switch accounts or log in again, and re-polls or reloads the cached policy verdict when that happens, rather than potentially keeping a stale verdict from the previous account.\n\n**Why**\n\nThis avoids a situation where switching accounts or logging in as someone else could leave stale rate-limit or compliance information from the previous account in effect.\n\n- Area: Policy Limits\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}