Skip to content

fix(query-core): use a hydrated query's current 'retry' options when it rejects #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
KATT wants to merge 7 commits into from
Closed

fix(query-core): use a hydrated query's current 'retry' options when it rejects #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
e5c9fca
fix(query-core): retry a hydrated query that rejects with its current…
cursoragent Nov 1, 2026
c60c712
test(query-core): dispose the clients of the hydrated rejection tests…
cursoragent Nov 1, 2026
2f740ee
test(query-core): unsubscribe the hydrated rejection tests' observers…
cursoragent Nov 2, 2026
e95e117
docs(query-core): use plainer words in the hydrated retry copy
cursoragent Nov 2, 2026
684374a
fix(query-core): retry a hydrated infinite query with its current opt…
cursoragent Nov 2, 2026
eb1b7f6
fix(query-core): only let retry options an observer set itself overri…
cursoragent Nov 2, 2026
9e4a941
test(query-core): resolve a fetch that joins a hydrated promise with …
cursoragent Nov 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/hydrated-rejection-retry.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@tanstack/query-core': patch
---

When a query hydrated while pending rejects, it now retries with the `retry` and `retryDelay` an observer set, if one mounted before the promise settled. Options the observer doesn't set itself, including client defaults, keep the values the query was hydrated with. Once an observer has mounted, a hydrated infinite query's retries run its `queryFn` from the first page, instead of replaying the rejected promise.
Loading
Loading