Client cache incorrectly resolves nested force-dynamic routes despite query parameter change (does not happen on / route)

[oreqizer]

Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/next-caching-5t73nd

To Reproduce

1. do next build && next start (works ok in next dev)
2. Go to / and see that the Load # link works (updating query parameters)
3. Go to /route and see that clicking Load # only works initially, and subsequently only every ~15s when client cache is invalidated
4. Comment out the export const dynamic = "force-dynamic"; in /route to fix the problem

Current vs. Expected behavior

Clicking Load # in nested routes marked as "force-dynamic" would correctly load server components and not hit client cache.

Verify canary release

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

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
Binaries:
  Node: 20.5.1
  npm: 9.8.0
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.0.1
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A

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

App Router, Data fetching (gS(S)P, getInitialProps), Routing (next/router, next/navigation, next/link)

Additional context

Next 14.0.1. I noticed this happening as soon as 13.5.x, but 13.4.12 worked fine.

[oreqizer]

Update: I noticed this is only happening with export const dynamic = "force-dynamic";. Removing this export gets rid of the issue

Updated the ticket

[samcx]

@oreqizer Thank you for sharing!

I was not able to replicate this with the latest stable v14.0.4—can you also confirm this?