---
title: Next.js encountered runtime data on a route that must be fully static
url: "https://nextjs.org/docs/messages/static-route-runtime"
docs_index: /docs/llms.txt
---



<div
  style={{
    padding: '1.25rem 1.5rem',
    border: '1px solid var(--ds-gray-400)',
    borderRadius: '12px',
    background: 'var(--ds-background-200)',
    margin: '1.5rem 0 2rem',
    fontSize: '0.95rem',
    lineHeight: '1.6',
  }}
>
  This error is part of the [Instant
  Navigations](https://nextjs.org/blog/next-16-3-instant-navigations) feature
  introduced in Next.js 16.3. If you're new to it, start with the [Ensuring
  instant navigations](/docs/app/guides/instant-navigation) guide.
</div>

A page or layout on this route exports [`ensureStatic`](/docs/app/api-reference/file-conventions/route-segment-config/ensureStatic) with the `'navigation'` value, requiring all server-rendered work for the route to complete during prerendering.

During [prerendering](/docs/app/glossary#prerendering), the page or layout read request-specific data from [`cookies()`](/docs/app/api-reference/functions/cookies), [`headers()`](/docs/app/api-reference/functions/headers), [`params`](/docs/app/api-reference/file-conventions/page#params-optional), or [`searchParams`](/docs/app/api-reference/file-conventions/page#searchparams-optional). Because these values are only available for a request, the route cannot be fully prerendered.

A [`use cache`](/docs/app/api-reference/directives/use-cache) scope also triggers this error when its [`expire`](/docs/app/api-reference/functions/cacheLife#expire) is under five minutes, [`stale`](/docs/app/api-reference/functions/cacheLife#stale) is under 30 seconds, or [`revalidate`](/docs/app/api-reference/functions/cacheLife#revalidate) is `0`.

Uncached [`fetch()`](https://developer.mozilla.org/en-US/docs/Web/API/Window/fetch) requests, database calls, and [`connection()`](/docs/app/api-reference/functions/connection) have different fixes. See [Uncached data on a route that must be fully static](/docs/messages/static-route-dynamic).

## Ways to fix this

<FixCardGrid>
  <FixCard
    group="remove"
    title="Remove the data access"
    href="#remove-the-data-access"
    snippets={[
      { text: 'async function Page() {' },
      { text: '- const store = await cookies()', highlight: true },
      { text: '  return <Content />' },
    ]}
  />
  <FixCard
    group="client"
    title="Read search parameters on the client"
    href="#read-search-parameters-on-the-client"
    snippets={[
      { text: "'use client'" },
      { text: 'const params = useSearchParams()', highlight: true },
      { text: "return <p>{params.get('q')}</p>" },
    ]}
  />
</FixCardGrid>

## Remove the data access

Choose this fix when the content does not need to vary by request. Replace the request-specific value with a value available during prerendering.

### Patterns

#### Remove the request-specific read

Remove the runtime API call and use a value that can be determined during prerendering.

```jsx filename="app/page.jsx"
export const ensureStatic = 'navigation'

export default function Page() {
  return <h1>My page</h1>
}
```

### Trade-off

Every visitor receives the same value because the route no longer reads request-specific data.

### Gotchas

- This fix applies to `cookies()`, `headers()`, and other removable reads. It does not provide replacement values when the content must vary by request.

## Read search parameters on the client

Choose this fix when only browser UI needs the query string.

### Patterns

#### Read the query string in a Client Component

Use [`useSearchParams()`](/docs/app/api-reference/functions/use-search-params) instead of the page's server-side `searchParams` prop:

```jsx filename="app/search/query.jsx"
'use client'

import { useSearchParams } from 'next/navigation'

export default function Query() {
  const searchParams = useSearchParams()
  return <p>Query: {searchParams.get('q')}</p>
}
```

Learn more: [`useSearchParams()`](/docs/app/api-reference/functions/use-search-params).

Render the Client Component inside [`Suspense`](https://react.dev/reference/react/Suspense). Do not pass the server's `searchParams` promise to it.

### Trade-off

The prerender includes the fallback, and the query-dependent UI renders in the browser.

### Gotchas

- Adding `'use client'` alone does not fix this error. Remove the server-side read and use the client hook.
- Do not pass the server's `searchParams` promise to the Client Component.
- This fix applies only to `searchParams`. It does not replace cookies, headers, or route parameters.

## Other options

### Extend the cache lifetime

Set `expire` to at least five minutes, `stale` to at least 30 seconds, and `revalidate` above `0`. Increase the lifetime only when serving shared, older content is acceptable.

Learn more: [`cacheLife`](/docs/app/api-reference/functions/cacheLife).

## Verifying the fix

After applying a fix, rerun [`next build`](/docs/app/api-reference/cli/next#next-build-options) and confirm that the route completes prerendering. If the error also appeared in [`next dev`](/docs/app/api-reference/cli/next#next-dev-options), reload the route and confirm that the overlay clears. Wrapping the access in Suspense or setting `instant = false` does not relax the fully static requirement.

In `next dev`, the error overlay points at the failing component with file paths and line numbers. Run [`next build --debug-prerender`](/docs/app/guides/building#debug-prerender-errors) for full user-frame stack traces and `next build --debug-build-paths /dashboard /settings` to iterate on specific routes.

## Remove the static requirement

The `'navigation'` value is usually set deliberately to guarantee static output for the entire server-rendered route. Removing it relaxes that requirement for every segment, not only the code that triggered this error.

If request-time rendering is intentional for this route, remove `ensureStatic = 'navigation'` from every page or layout that sets it. The route then follows the ordinary [Cache Components](/docs/app/getting-started/caching) rendering rules.

Learn more: [Combining `ensureStatic` levels across layouts and pages](/docs/app/api-reference/file-conventions/route-segment-config/ensureStatic#combining-levels-across-layouts-and-pages).

## Related validation errors

See [Instant Navigation validation errors](/docs/messages/instant-navigation-validation) for the complete reference.