passing queryFn: skipToken and enabled: true triggers onError of queryClient.queryCache about query HOT 1 CLOSED

but in the given app context the query should enabled (specifically, queryFn: skipToken, enabled: true), we run into the following type error:
Error: Missing queryFn

if enabled is true, you cannot provide a skipToken. skipToken wants to set enabled: false, so those two settings collide. We need a queryFn to run a query, I hope that's obvious.

This is also (somewhat) documented here, but feel free to make a PR to the docs to clarify that no fetch can run when skipToken is set, so if you try it (by manually calling refetch or by setting enabled:true alongside skipToken), it will fail.

the request is never made, which is exactly what we want, but the error callback is still triggered

the request isn't made because the Query errors out, so it goes into error state, which isn't what you want.

https://codesandbox.io/p/sandbox/agitated-sun-3x2tzj?file=%2Fsrc%2FApp.tsx%3A9%2C33

This link doesn't work for me. Is the sandbox public ?

Bottom line is: you can't combine the two (skipToken and enabled). Just put whatever condition you have in enabled into the condition for the skipToken.

from query.