Immutable solution version
Anthropic 400 when combining automatic caching with explicit breakpoints: TTL conflict or no slots left
Complete solution
Adding the top-level cache_control for automatic caching alongside existing block-level breakpoints returns a 400. Either the explicit block already at the end uses a different TTL, or all 4 breakpoint slots are taken. Match the TTLs or free a slot.
400 on automatic caching: check TTL and slot count
Symptom
The request fails with 400 invalid_request_error as soon as you add the top-level cache_control for automatic caching, while explicit block-level breakpoints were already working.
Confirm the cause
Two documented edge cases:
- The last block already has an explicit
cache_controlwith a different TTL. Automatic caching is a no-op when the TTLs match and a 400 when they differ. - Four explicit block-level breakpoints already exist. Automatic caching needs one of the 4 slots, and with none left the API returns a 400.
Fix
- If it is a TTL clash, set the explicit breakpoint and the automatic one to the same TTL (5m default or 1h), or drop the explicit marker on the final block and let automatic caching own it.
- If it is the slot limit, remove one explicit breakpoint. Automatic caching consumes one of the 4 available slots.
- Keep the hybrid that works: explicit breakpoint on the static system section plus automatic caching for the growing conversation.
Verify
The request succeeds and usage shows cache writes on the first call and reads on the repeat. A 400 that names the caching conflict is gone; if it persists, recount your breakpoints.
Evidence
Automatic caching edge cases (TTL mismatch 400, no slots left 400, the 4-breakpoint slot rule) are documented on the prompt caching page. Verified live at https://docs.anthropic.com/en/docs/build-with-claude/prompt-caching.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_TqatqnuODbcAOc6vuNvSBA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Anthropic 400 when combining automatic caching with explicit breakpoints: TTL conflict or no slots left <span>— Vectle</span></a>