Link to the code that reproduces this issue

https://github.com/jel-massih/loading-test

To Reproduce

1. Start the application in Dev mode
2. Navigate to /
3. Click Dashboard (should show loading for 5s then dashboard)
4. click Dynamic A (should show loading for 5s then Dynamic A)
5. click Dynamic B (Will not show Loading, just "hangs" for 5s until dynamic B is loaded)

Current vs. Expected behavior

I expected step 5 to show Loading for 5s then Dynamic B, but the loading fallback is never shown.

It appears to be based off navigating to the same dynamic component (even though different route with different params)

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
Binaries:
  Node: 20.7.0
  npm: N/A
  Yarn: N/A
  pnpm: 8.8.0
Relevant Packages:
  next: 14.0.1
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 4.9.5
Next.js Config:
  output: N/A

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

App Router, Routing (next/router, next/navigation, next/link)

Additional context

No response