Skip to content

Parallel routes not working inside dynamic page, when in same segment #84813

@FacundoSpira

Description

@FacundoSpira

Link to the code that reproduces this issue

https://github.com/FacundoSpira/parallel-routes-error

To Reproduce

I have the following file structure:

app/
├─ groups/
│  ├─ [id]/
│  │  ├─ new/
│  │  │  ├─ page.tsx
│  │  ├─ page.tsx
├─ @modal/
│  ├─ (.)groups/
│  │  ├─ [id]/
│  │  │  ├─ new/
│  │  │  │  ├─ page.tsx
│  ├─ default.tsx
├─ page.tsx

In both the / and groups/[id] routes I have Links to groups/123/new. When clicking it from the / page, it correctly opens the parallel route, but when clicking it from the groups/123 page, it's redirecting to the actual page, and not the parallel route. This only happens when the route is inside a dynamic group ([id]).

Current vs. Expected behavior

Expected: both links should open the parallel route.

Additional note: this started happening after upgrading from the 15.6.0-canary.53 version. The reproduction example has two branches:

  • main: using next version 16.0.0-canary.3
  • 15.6.0-canary.53: using 15.6.0-canary.53. Parallel routes work fine here in both cases

16.0.0-canary.3

Screen.Recording.2025-10-13.at.12.09.36.AM.mov

15.6.0-canary.53

Screen.Recording.2025-10-13.at.12.12.24.AM.mov

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:39 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T8103
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.12.2
  npm: 10.5.0
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 16.0.0-canary.3 // Latest available version is detected (16.0.0-canary.3).
  eslint-config-next: 16.0.0-canary.3
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Parallel & Intercepting Routes

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

Additional context

No response

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions