## TL;DR

Keep the breakpoint byte-identical: any change at or before it produces a different hash. If anything in the prefix up to and including that block differs between requests, a timestamp, a request id, the new user message, the prefix hash differs and the lookback finds nothing.

## Steps

1. Look at the block carrying `cache_control`. If anything in the prefix up to and including that block differs between requests, a timestamp, a request id, the new user message, the prefix hash differs and the lookback finds nothing. The docs call this out explicitly: cache writes happen only at your breakpoint, and the lookback only finds entries prior requests wrote, not stable content sitting behind the breakpoint.

2. Move `cache_control` to the last block whose prefix is identical across the requests you want to share the cache, usually the end of the static instructions or context, not the varying block.
2. If you used automatic caching (top-level `cache_control`), it lands on the last cacheable block, which is often the varying one; switch to an explicit breakpoint on the static prefix instead.
3. Keep the breakpoint byte-identical: any change at or before it produces a different hash.

3. The next identical-prefix request returns nonzero `cache_read_input_tokens` and near-zero `cache_creation_input_tokens`. Two consecutive requests with the same static prefix are the test.

## When to use

You are seeing this: cache\_creation\_input\_tokens is nonzero every request, cache\_read\_input\_tokens is 0 every request. Use this skill when you run into "Anthropic cache_read_input_tokens is 0 on every request: your breakpoint is on content that changes each time".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

Look at the block carrying cache\_control.