Browser back/foward doesn't rerun component code

[Rc85]

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/8sfnt3

To Reproduce

1. Make sure you are on the "Start Dev Server" terminal so you can see console logs.
2. In the preview, you should see the next.js home page. Notice in terminal there will be console log showing root layout and loading home.
3. Add /project to the end of the urls and hit Enter (url should look like https://8sfnt3-3000.csb.app/project). You should see console log showing root layout and loading project.
4. Then press the back button on your mouse or using alt + left arrow (windows) or cmd + left arrow (mac).
5. Notice that there are no console logs. If you modify the project/page.tsx file and then go back to /project, it's still showing the previous version.

Current vs. Expected behavior

Current behavior is that component codes do not rerun when directly accessing a url and then using back and forward. I have codes like useEffect that needs to run to initialize the component.

Expected behavior should run the component's code like useEffect and other logic.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro N
  Available memory (MB): 32699
  Available CPU cores: 16
Binaries:
  Node: 22.14.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.2.1 // Latest available version is detected (16.2.1).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: N/A
Next.js Config:
  output: N/A

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

Loading UI and Streaming

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

next dev (local)

[widavies]

Same bug here - I see this when duplicating a tab when developing. The page sort of loads from the SSR cache - but none of the client side JS is run and nothing is interactive. The console is completely blank - no console.log's run anywhere.

[jimrandomh]

Related: #91540 and #86577 .

[christopherjohnson3028-stack]

Thank you for linking those previous reports (#91540 and #86577).

…

On Tue, Mar 31, 2026, 1:26 AM James Babcock ***@***.***> wrote: *jimrandomh* left a comment (vercel/next.js#91982) <#91982 (comment)> Previous reports: #91540 <#91540> and #86577 <#86577> . — Reply to this email directly, view it on GitHub <#91982?email_source=notifications&email_token=B67D5GIUHT7DDBUF2EFCLQ34TNQI5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGAZDGMBUGY4KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4160230468>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B67D5GK6SSWINPJ2MWEYZ6D4TNQI5AVCNFSM6AAAAACXBSORGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNRQGIZTANBWHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[victorlangston123-droid]

I am also experiencing this issue. I’ve noticed the same behavior where the page appears to load from the SSR cache, but the client-side JS does not execute and the page remains non-interactive. On Tue, Mar 31, 2026, 8:39 AM christopherjohnson3028-stack < ***@***.***> wrote:

…

*christopherjohnson3028-stack* left a comment (vercel/next.js#91982) <#91982 (comment)> Thank you for linking those previous reports (#91540 and #86577). On Tue, Mar 31, 2026, 1:26 AM James Babcock ***@***.***> wrote: > *jimrandomh* left a comment (vercel/next.js#91982) > <#91982 (comment)> > > Previous reports: #91540 <#91540> > and #86577 <#86577> . > > — > Reply to this email directly, view it on GitHub > < #91982?email_source=notifications&email_token=B67D5GIUHT7DDBUF2EFCLQ34TNQI5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGAZDGMBUGY4KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4160230468>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/B67D5GK6SSWINPJ2MWEYZ6D4TNQI5AVCNFSM6AAAAACXBSORGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNRQGIZTANBWHA> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > — Reply to this email directly, view it on GitHub <#91982?email_source=notifications&email_token=CAXXQK57MRDYKQN45PNL6AL4TPDAHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGI3TCOJTHAYKM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4162719380>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CAXXQK6CJTTBXGHKYVBW6SL4TPDAHAVCNFSM6AAAAACXBSORGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNRSG4YTSMZYGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[icyJoseph]

@jimrandomh this is a different bug - it doesn't need Cache Components. This one is related: #92238 - but I haven't verified same root cause, albeit, it is nearly the same issue description.

[matthanes]

I am having the same issue. My header and footer do not render when I go back or forward.

[icyJoseph]

@matthanes are you using Cache Components? And if this back forward, after navigating via anchor tag?

[matthanes]

@icyJoseph no Cache Components. Just anchor tags.

[icyJoseph]

No next/link right? so essentially hard navigations, I forgot to ask that further in my previous comment

[matthanes]

@icyJoseph correct, just normal <a> tags

[icyJoseph]

Ok then, #92238 is also the same issue too. Gonna remind the team about this. We narrowed it down to a PR, but the behavior is still strange. Safari hard navs work fine, but FF and Chrome are showing this issue.

[luan-services]

Same here problem here, i was going insane for 8 hours straight trying to figure out why my better auth session suddenly dissapear.

Gravando.2026-04-12.121338.mp4