Partial suspense key not working

[der-daniel]

Link to the code that reproduces this issue

https://github.com/der-daniel/partial-suspense-key

To Reproduce

1. Fire Up the Application
2. There are two search params key1 and key2
3. There are two server components which are using the route in /api. The route simply returns the key.
4. Use the buttons on the page to either change one of the search params or both.

Current vs. Expected behavior

Current behavior:

• If I change both keys, the suspense triggers both fallback uis for loading the api endpoint inside the server components. Everything is responsive and fast.
• If I only change one of the keys no fallback ui is triggered and the ui is blocked, i.e. the url only changes after all api requests are finished.

Expected behavior:

• If I only change one of the keys, I expect only the respective suspense component triggers the fallback ui while the other stays the same. Moreover the ui should not block and wait for the requests to finish.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 18.19.0
  npm: 10.2.3
  Yarn: N/A
  pnpm: 9.4.0
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.3
Next.js Config:

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

Navigation

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

next dev (local)

Additional context

No response