Route used revalidatePath during render Next.js Origin: On your device Last updated 5 Nov 2026

Next.js: Error: Route /blog used "revalidatePath /blog" during render which is unsupported. It must happen outside of renders and cached functions

revalidatePath/revalidateTag was called while rendering a page or component, not from an action or route handler.

Exact message you may see used "revalidatePath /blog" during render which is unsupportedRoute used "revalidatePath" during render which is unsupported. To ensure revalidation is performed consistently it must always happen outside of renders and cached functionsused revalidateTag during render which is unsupportedrevalidatePath during render unsupported
Explore the map of this error Full error map →
Seen on: Next.js React

Meaning

Revalidation is a mutation and may only run in Server Actions, Route Handlers or webhooks. Move the call to the action that changes data. For time-based refresh use export const revalidate = 60 or fetch(..., { next: { revalidate: 60 } }).

Common causes

  • Calling revalidatePath inside a Server Component render
  • Inside unstable_cache or cached functions
  • During generateMetadata/layout
  • In a data-fetching helper used by pages
  • Called from a loop at render time

⚡ Quick fix

  1. Call it from a Server Action or Route Handler after the mutation
  2. Use revalidate settings for time-based caching
  3. Don't call from helpers used during render

Detailed fix by platform

Next.js

  1. "use server"; export async function savePost(d: FormData) { await db.save(d); revalidatePath("/blog"); }

How to diagnose

  1. Context — Render or action?
  2. Cached — Inside cached fn?
  3. Alternative — Time-based revalidate?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

Conflicting app and page file was found — Next.js: ⨯ Conflicting app and page file was found, please remove the conflicting files to continue: "pages/index.tsx" - "app/page.tsx" (Next.js)Conflicting app and p…Dynamic server usage — Error: Dynamic server usage: Route /x couldn't be rendered statically because it used `cookies` (React)Dynamic server usageFailed to set Next.js data cache, items over 2MB can not be cached — Next.js: Failed to set Next.js data cache for https://api.example.com/data, items over 2MB can not be cached (2437412 bytes) (Next.js)Failed to set Next.js…next build: fetch failed ECONNREFUSED (build-time API) — Next.js: Error occurred prerendering page "/blog" TypeError: fetch failed { cause: Error: connect ECONNREFUSED 127.0.0.1:3000 } (Next.js)next build: fetch fai…next build: JavaScript heap out of memory — Next.js: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory (during next build) (Next.js)next build: JavaScrip…Server actions must be async functions — Next.js: Error: Server actions must be async functions (Next.js)Server actions must b…Used cookies/headers inside a function cached with unstable_cache — Next.js: Route used `cookies()` inside a function cached with `unstable_cache(...)`. Accessing Dynamic data sources inside a cache scope is not supported (Next.js)Used cookies/headers …Route use…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.