Same options, same output? The 48h document cache is serving stale parses

TL;DR

If tweaking parsing_instruction or options changes nothing in the output, you are reading the cached result. LlamaParse caches by document hash for ~48h, so re-submitting the same file returns the old parse for free. Force a fresh parse with the invalidate-cache option when iterating on instructions.

Fix

If tweaking parsing_instruction or options changes nothing in the output, you are reading the cached result. LlamaParse caches by document hash for ~48h, so re-submitting the same file returns the old parse for free. Force a fresh parse with the invalidate-cache option when iterating on instructions. Conversely, lean on the cache deliberately: re-running a pipeline over unchanged documents costs nothing.

Context: LlamaParse field notes (document-parsing SKILL.md): parse results are cached server-side for about 48 hours keyed by document hash, so re-parsing the same document is free - but it also means changed parsing options will not take effect on a re-parse unless you invalidate the cache.

Matched source

Source: Published skill Original query: "Same options, same output? The 48h document cache is serving stale parses" Key terms: cache, document, options, output, parses, same, serving, stale

When to use this

• Use this when your task, error, or question matches the title above and the setup in the Fix section.

When not to use this

• Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

Compatibility

The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.

Source: LlamaParse field notes (document-parsing SKILL.md): parse results are cached server-side for about 48 hours keyed by document hash, so re-parsing the same document is free - but it also means changed parsing options will not take effect on a re-parse unless you invalidate the cache.

Verified resolution: If tweaking parsing_instruction or options changes nothing in the output, you are reading the cached result. LlamaParse caches by document hash for ~48h, so re-submitting the same file returns the old parse for free. Force a fresh parse with the invalidate-cache option when iterating on instructions. Conversely, lean on the cache deliberately: re-running a pipeline over unchanged documents costs nothing.

Source URL: https://github.com/lizo-roadtown/tapestry/blob/HEAD/integrations/claude-code/tapestry-patterns/skills/document-parsing/SKILL.md