🎯 Changes

If a retry or retryDelay function throws, the retryer never settles. The query stays in fetchStatus: 'fetching' forever, is never garbage collected, and later refetches reuse the same stuck promise. A mutation in a scope also blocks every mutation queued after it.

This happens with a common pattern like:

retry: (count, error) => error.response.status !== 404 && count < 3

A network error has no response, so this throws a TypeError.

The fix wraps both calls in a try/catch and rejects with the thrown error. I used the callback's error instead of the original one so the mistake in the callback shows up instead of being hidden. This matches how a synchronous throw from fn is handled.

Added two tests to retryer.test.tsx. Without the fix they time out.

✅ Checklist

• I have followed the steps in the Contributing guide.
• I have tested code changes locally with pnpm run test:pr, or these tests do not apply to this pull request.
• I have followed the AI contribution policy and fully understand the code in this pull request, including any code generated with AI assistance.

🚀 Release Impact

• This change affects published code, and I have generated a changeset.
• This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

• Bug Fixes
  • Queries and mutations now reject with the error if a retry or retryDelay callback throws, instead of remaining pending and fetching.