{"version":"2.1.227","anchor":"managed-policy-limits-can-be-cached-through-the-storage-back","canonical_anchor":"managed-policy-limits-can-be-cached-through-the-storage-back","heading":"Managed policy limits can be cached through the storage backend","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/managed-policy-limits-can-be-cached-through-the-storage-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Managed policy limits can be cached through the storage backend\n\nManaged policy limits can be cached through the storage backend, falling back to the cache file.\n\n**What**\n\nThe loader for managed policy limits can now prime its cache from a storage backend at startup and write and delete through it, under a `policy-limits` key. If the prime read fails or the cached blob is too large it logs and falls back to reading the raw cache file as before. Polling, stale-cache fallback and the existing telemetry are unchanged.\n\n**Details**\n\n- the storage path is used only when a storage backend is supplied; otherwise the file path is used\n\n**Evidence**\n\n`Policy limits: prime skipped (oversize cache); raw cache read stays`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}