vercel/next.js · error · Error

Invalid interception route: ${path}. Must be in the format /

Error message

Invalid interception route: ${path}. Must be in the format /<intercepting route>/(..|...|..)(..)/<intercepted route>

What it means

Parser guard in extractInterceptionRouteInformation: walking the path segments found an interception marker (.., ...,(..)(..)) but could not split the path into a non-empty intercepting route and intercepted route around it. The generated interception-route pathname is structurally invalid; the expected format is spelled out in the message.

Source

Thrown at packages/next/src/shared/lib/router/utils/interception-routes.ts:55

  for (const segment of path.split('/')) {
    marker = INTERCEPTION_ROUTE_MARKERS.find((m) => segment.startsWith(m))
    if (marker) {
      ;[interceptingRoute, interceptedRoute] = path.split(marker, 2)
      break
    }
  }

  if (!interceptingRoute || !marker || !interceptedRoute) {
    throw new Error(
      `Invalid interception route: ${path}. Must be in the format /<intercepting route>/(..|...|..)(..)/<intercepted route>`
    )
  }

View on GitHub (pinned to 0eb3775416)

Solutions

  1. Format the route as /<intercepting>/(..|...|..)(..)/<intercepted>.
Defensive patterns

Strategy: validation

When it happens

Trigger: An interception route path does not match the required marker format.

Common situations: A route segment using (..), (...), or (..)(..) in an invalid arrangement.

AI-assisted analysis of vercel/next.js@0eb3775416 (2026-08-19). Data as JSON: /api/errors/72781cb2c189b4b2. Report an issue: GitHub.