{"version":"2.1.273","anchor":"policy-limits-credentialprincipal-check-now-threads-a-reaso","canonical_anchor":"policy-limits-credentialprincipal-check-now-threads-a-reaso","heading":"Policy-limits credential\/principal check now threads a reason through polling","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/policy-limits-credentialprincipal-check-now-threads-a-reaso","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Policy-limits credential\/principal check now threads a reason through polling\n\nPolicy-limits re-checks now record why they were triggered, such as a credential change or the hourly poll\n\n**Unclear.** The finding doesn't confirm what the reason is used for beyond being passed through the polling calls.\n\n**What**\n\nThe internal checks that re-fetch your account's policy limits now carry an explicit reason label through the process, for example `credential_change` (the default when credentials change) or `hourly_poll` (the default for the regular scheduled check).\n\n**Why**\n\nThis is likely for internal logging or telemetry, to distinguish why a policy-limits re-check happened, rather than changing what happens for the reader directly.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}