Framework semantic default

Next.js revalidateTag profile max stale while revalidate

A mutation invalidates data at an unexpected time or serves stale content.

search-observedNext.jsWeb frameworkFramework semantic defaultnext16

Agent Quick Fix

Local code often type-checks under both old and new framework semantics; the failure depends on the installed framework version and current runtime defaults.

Product: Next.js
Current-contract area: Next.js 16 revalidateTag semantics differ from old stale-while-revalidate use
Likely root cause: A mutation invalidates data at an unexpected time or serves stale content.
Repair direction: Verifier checks behavior across multiple requests/build modes, not merely compilation. Check request count, response freshness, and render behavior over multiple calls.

Validation Status

Codex searched organically in the validation run. No no-web counterfactual is attached to this page yet.

Symptom

A mutation invalidates data at an unexpected time or serves stale content.

Why This Happens

Local code often type-checks under both old and new framework semantics; the failure depends on the installed framework version and current runtime defaults.

Verification

Verifier checks behavior across multiple requests/build modes, not merely compilation. Check request count, response freshness, and render behavior over multiple calls.

Common Wrong Fixes

Changing local code without checking the current external contract.
Retrying the same install, build, or API call with no version/source change.
Applying a broad unsafe bypass when a narrow compatibility fix is available.

Codex Search Keywords

These are the search terms observed in a neutral Codex validation run for this failure shape.

site:nextjs.org/docs revalidateTag Next.js 16 stale-while-revalidate profile="max"
Next.js revalidateTag profile max stale while revalidate
https://nextjs.org/docs/app/api-reference/functions/revalidateTag
https://nextjs.org/docs/app/api-reference/functions/updateTag