{"version":"2.1.293","anchor":"1h-cache-ttl-also-disabled-when-using-overage","canonical_anchor":"1h-cache-ttl-also-disabled-when-using-overage","heading":"Prompt caching behaves differently while using overage","tier":"notice","area":"Prompt Cache","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/1h-cache-ttl-also-disabled-when-using-overage","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Prompt caching behaves differently while using overage\n\nWhen an account is using overage, the 1-hour prompt cache is turned off and a cache-touch step is skipped\n\n**Unclear.** It is not clear which other condition must also hold for this to apply.\n\n**What**\n\nThe prompt cache keeps recent conversation text on the server so it does not have to be processed again. Overage, also called extra usage, is usage beyond what your plan includes. Two cache checks now look at whether the account is using overage (`isUsingOverage`).\n\n- The 1-hour cache lifetime for subscribers is now off when the account is using overage. This extra condition is added where a flag was already checked.\n\n- A step that touches the cache to keep it alive no longer runs while the account is using overage.\n\n**Why**\n\nIf you are a subscriber working in overage, cached text may expire sooner than the 1-hour lifetime. More text may then be processed again, which could change what a session costs.\n\n- Area: Prompt Cache\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}