Skip to content

fix(query): retry failed reads after hydration - #727

Open
yuxino wants to merge 1 commit into
solidjs:nextfrom
febug:fix/query-retry-after-rejection
Open

yuxino wants to merge 1 commit into
solidjs:nextfrom
febug:fix/query-retry-after-rejection

Conversation

@yuxino

@yuxino yuxino commented Nov 15, 2026

Copy link
Copy Markdown

Fixes #726.

When a query failed, hitting Retry in an <Errored> fallback could read the same rejected promise from the router cache. The fallback stayed visible and the query did not run again.

A rejected client entry remains available while Solid claims the server-rendered fallback. Outside hydration, the next read can fetch again immediately. Concurrent reads still share their in-flight request, and an older rejected request leaves a newer cache value intact.

Verified the failing retry against the published 2.0.0-next.44 package. Added regressions for clicking Retry and for reusing a rejected server flight during hydration before retrying it. The client and server suites, type checks, and build pass.

@changeset-bot

changeset-bot Bot commented Nov 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 3272eff

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@solidjs/router Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant