Repository navigation
fix(next/client): fall back to full-page navigation on segment cache fetch failure - #97815
Open
patrickswedish wants to merge 1 commit into
Open
patrickswedish wants to merge 1 commit into
patrickswedish wants to merge 1 commit into
Conversation
patrickswedish
force-pushed
the
fix/segment-cache-navigation-failure-97807
branch
from
October 22, 2026 05:10
eb2af75 to
b3203e9
Compare
patrickswedish
changed the title
…fetch failure Fixes vercel#97807 # Conflicts: # packages/next/src/client/components/app-router-state.ts
patrickswedish
force-pushed
the
fix/segment-cache-navigation-failure-97807
branch
from
November 2, 2026 22:48
b3203e9 to
0e38369
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #97807
What?
When segment cache payload fetching encounters a network error or rejected server response, fall back to a full-page (MPA) browser navigation instead of silently swallowing the error and freezing user navigation.
Why?
Fixes #97807.
Currently, when a prefetch or dynamic RSC payload fetch stalls or rejects with a network error,
avigateImpl(...).catch(() => state)\ returns the current state with zero fallback. The user's click is permanently dropped, leaving them stuck on the previous view.
Intentional aborts (e.g. \AbortError, \TimeoutError) are preserved so superseded navigations still retain state. For actual network failures, falling back to \completeHardNavigation\ restores expected web semantics.
How?
avigateImpl.catch().