Runtime logs now show a Cache Reason explaining why a request wasn't a fresh cache hit, for example a time-based or tag-based revalidation. Use cache reasons to debug misses and improve your hit rate.
Cache reasons appear for any response the CDN can cache, including ISR, Partial Prerendering, and functions that set a
Open the Logs tab and select a request to see the reason alongside its cache status. Each status and reason links to its entry in the Cache Status and Reasons reference.
Cache reason is available in
Learn more about cache statuses and reasons.
Read more
Continue reading...
Cache reasons appear for any response the CDN can cache, including ISR, Partial Prerendering, and functions that set a
Cache-Control header with directives like stale-while-revalidate. Responses rendered dynamically on every request don't have a cache reason.Cache status | Possible reasons |
MISS | Cold, Request collapsed, Error |
BYPASS | Draft Mode, Prerender Bypass, Crawler |
STALE | Time-based revalidation, Tag-based invalidation, Revalidation error |
REVALIDATED | Tag-based deletion |
Open the Logs tab and select a request to see the reason alongside its cache status. Each status and reason links to its entry in the Cache Status and Reasons reference.
From the CLI
Cache reason is available in
vercel logs, vercel metrics, and Vercel plugin's cdn-caching skill:Learn more about cache statuses and reasons.
Read more
Continue reading...