Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix UpdateTag is causing hard refresh [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#93277•Fetched 2026-04-28 06:23:29
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
lucas-garridolucas-garrido
Participants
lucas-garridolucas-garrido
Timeline (top)
labeled ×2issue_type_added ×1

Error Message

The updateTag is causing hard refresh ending to a 404 error page.

Code Example

Operating System:
  Platform: linux
  Arch: x64
  Version: #50~22.04.1-Ubuntu SMP Wed Dec  3 15:13:22 UTC 2025
  Available memory (MB): 7944
  Available CPU cores: 2
Binaries:
  Node: 24.14.0
  npm: 11.9.0
  Yarn: 1.22.22
  pnpm: 10.32.1
Relevant Packages:
  next: 16.2.4 // Latest available version is detected (16.2.4).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/lucas-garrido/nextjs-issue-reproduction

To Reproduce

I'm using parallel routes modals

  1. Start the application
  2. Go to /test url
  3. Open the first Modal => Go to detail page => Open second modal => Click on update tag button
<img width="1122" height="573" alt="Image" src="https://github.com/user-attachments/assets/46c2f75b-6d1d-45e0-84b7-8dc3a0c2c4c8" />

Current vs. Expected behavior

The updateTag is causing hard refresh ending to a 404 error page. This issue is related to the navigation flow if i start the app directly on the detail page (/test/42) the updateTag is working as expected

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #50~22.04.1-Ubuntu SMP Wed Dec  3 15:13:22 UTC 2025
  Available memory (MB): 7944
  Available CPU cores: 2
Binaries:
  Node: 24.14.0
  npm: 11.9.0
  Yarn: 1.22.22
  pnpm: 10.32.1
Relevant Packages:
  next: 16.2.4 // Latest available version is detected (16.2.4).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

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

Parallel & Intercepting Routes, Server Actions

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

next dev (local), next start (local)

Additional context

No response

extent analysis

TL;DR

The issue can be fixed by adjusting the navigation flow to prevent hard refreshes when using parallel routes modals.

Guidance

  • Review the updateTag function to ensure it's not causing a full page reload, which could lead to the 404 error.
  • Verify that the next configuration is set up correctly to handle parallel routes and server actions.
  • Check the modal implementation to see if it's possible to update the tag without triggering a full page reload.
  • Test the application by starting directly on the detail page (/test/42) to see if the issue is specific to the navigation flow.

Example

No code snippet is provided as the issue lacks specific implementation details.

Notes

The issue seems to be related to the navigation flow and parallel routes modals. Further investigation is needed to determine the root cause.

Recommendation

Apply a workaround to prevent hard refreshes when using parallel routes modals, as the root cause is not immediately clear.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#agent setup#task chaining#parallel task#integration issue#index setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix UpdateTag is causing hard refresh [1 participants]