{"version":"2.1.212","anchor":"cache-control-demotion-on-mid-conversation-system","canonical_anchor":"cache-control-demotion-on-mid-conversation-system","heading":"Cache Control Demotion on Mid-Conversation System","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.212\/e\/cache-control-demotion-on-mid-conversation-system","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.212","markdown":"### Cache Control Demotion on Mid-Conversation System\n\nWhen the API rejects `cache_control` on a mid-conversation system turn with an \"additional properties\", \"unknown field\", or similar error, Claude now detects this and demotes the cache breakpoint to the trailing message rather than the system block. Logged as: `[mid-conv-system] proxy rejected cache_control on the api_system tail \u2014 demoting the breakpoint to the trailing message for this conversation`.\n\n**Evidence**\n\n`\"retry:api-system-cache-demote\"` (search for `\"q9i\"`)"}