From c26f2dfb897ef9775d7357fa5c87b1789ae689f9 Mon Sep 17 00:00:00 2001 From: varunchandrashekar05 Date: Sun, 26 Oct 2025 22:47:16 +0530 Subject: [PATCH] docs: improve skipToken and refetch incompatibility warning - Add detailed explanation of Missing queryFn error when using refetch() with skipToken - Provide clear guidance to use enabled: false instead for manual refetching - Systematic fix affects all frameworks (Vue, Angular, Solid) via inheritance Fixes #7599 --- docs/framework/react/guides/disabling-queries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/react/guides/disabling-queries.md b/docs/framework/react/guides/disabling-queries.md index 93ff4ee36c..8b5df15748 100644 --- a/docs/framework/react/guides/disabling-queries.md +++ b/docs/framework/react/guides/disabling-queries.md @@ -97,7 +97,7 @@ so it will only be true if the query is currently fetching for the first time. If you are using TypeScript, you can use the `skipToken` to disable a query. This is useful when you want to disable a query based on a condition, but you still want to keep the query to be type safe. -> IMPORTANT: `refetch` from `useQuery` will not work with `skipToken`. Other than that, `skipToken` works the same as `enabled: false`. +> **IMPORTANT**: `refetch` from `useQuery` will not work with `skipToken`. Calling `refetch()` on a query that uses `skipToken` will result in a `Missing queryFn` error because there is no valid query function to execute. If you need to manually trigger queries, consider using `enabled: false` instead, which allows `refetch()` to work properly. Other than this limitation, `skipToken` works the same as `enabled: false`. [//]: # 'Example3'