{"version":"2.1.300","anchor":"cache-tier-detection-order-swapped-5m-before-1h","canonical_anchor":"cache-tier-detection-order-swapped-5m-before-1h","heading":"Mixed cache responses are now labelled \"5m\" instead of \"1h\"","tier":"internal","area":"Prompt Caching","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/cache-tier-detection-order-swapped-5m-before-1h","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Mixed cache responses are now labelled \"5m\" instead of \"1h\"\n\nWhen a response uses both prompt cache lengths, Claude Code now labels its cache time as 5 minutes instead of 1 hour\n\n**What**\n\nPrompt caching lets the API reuse earlier parts of a conversation instead of processing them again. A cached part is kept for either 5 minutes or 1 hour. Claude Code labels each response with the cache length it used.\n\nIt now checks for 5-minute cache use first. A response that used both lengths is now labelled \"5m\", where before it was labelled \"1h\".\n\n**Why**\n\nAnything that shows or records the cache length will now show 5 minutes for those mixed responses.\n\n- Area: Prompt Caching\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}