Failed to fetch RSC payload for <url> Falling back to browser navigation. TypeError: Failed to fetch

[imNotTheDevYouAreLookingFor]

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/github/vercel/next.js/tree/canary/examples/reproduction-template

To Reproduce

Seems like this can be reproduced on any nextjs site but used nextjs.org as an example: 1 Go to https://nextjs.org/docs 2 Open console and click "preserve log" 3 Spam cmd+shift+r 4 Look at error messages

Current vs. Expected behavior

This issue seem to exist in all nextjs sites and it's causing cpu spikes in the server (at least for us)

Verify canary release

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

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:59:33 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T8112
Binaries:
  Node: 20.1.0
  npm: 9.6.4
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.0.4
  eslint-config-next: 13.0.0
  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)

Not sure

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

Other (Deployed)

Additional context

No response

[kelvinCJJ]

I am also facing this, would be great to get a resolution as soon as possible

[Semkoo]

This is also happening with on the latest version of Next 14.1.0

[Semkoo]

This is also happening with on the latest version of Next 14.1.0

Clearing the cache remove the error for me btw

[imNotTheDevYouAreLookingFor]

This is also happening with on the latest version of Next 14.1.0

Clearing the cache remove the error for me btw

I guess it's just temporary though?

[Semkoo]

This is also happening with on the latest version of Next 14.1.0

Clearing the cache remove the error for me btw

I guess it's just temporary though?

Haven't seen it since, where are you hosting your Next?

[landsman]

I can see this error as well when I click fast on Links. It's probably an unfinished prefetch of the page.

[Harit007x]

I am also facing the same issue.

[musme]

I also facing the same error. It throws on page load.

[vanoMekantsishvili]

Any other solutions other then clearing cache does anyone found yet ? Thank you.

[DonikaV]

Same here, Nextjs 14.2.5

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[garrettboatman]

Getting thousands of these errors from iOS users. Is this an RSC thing? NextJS thing?

[therealtgd]

Same thing happening to me.

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[tonyfarney]

In Next 14.2.13 this is still happening

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[jakehopking]

Getting this error with Next 15 Canary 190 (may have been prior too, but I've just started building the project for prod). I am using the custom CacheHandler from @neshca/cache-handler. However this was an intermittent issue when using next's built-in caching too. Setting every use of <Link prefetch={false} ... has made the effect less pronounced, but there are still pages where the page enters a loading loop with Failed to fetch RSC payload for http://localhost:3002/<some-pathname> Falling back to browser navigation. TypeError: Failed to fetch printed to the console repeatedly.

[QinZhen001]

I am also facing the same issue.

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[MattisAbrahamsson]

We're seeing a lot of these issues in Sentry, this console message is always followed by an error saying: TypeError: Cannot read properties of undefined (reading 'call')