{"version":"2.1.271","anchor":"policy-limits-fetch-now-tracks-whether-the-accountprincipal","canonical_anchor":"policy-limits-fetch-now-tracks-whether-the-accountprincipal","heading":"Policy-limits fetch now tracks whether the account\/principal changed mid-request","tier":"internal","area":"Policy Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/policy-limits-fetch-now-tracks-whether-the-accountprincipal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Policy-limits fetch now tracks whether the account\/principal changed mid-request\n\nPolicy-limits requests now record whether the logged-in account changed mid-request\n\n**What**\n\nThe internal request that fetches policy limits (rules about what an account is allowed to do) now records three extra pieces of information on every outcome, whether it succeeds, returns unchanged data, fails to parse, or errors out: which account was active when the request was sent, which account was being asked about, and whether the account changed between the start and end of the request.\n\n**Why**\n\nThis is internal bookkeeping that helps distinguish a genuine policy problem from a case where the user switched accounts mid-request, which is not something end users will directly see.\n\n- Area: Policy Limits\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}