tanstack-query-intent-framework-handle-status-and-errors

Core Patterns

Prefer data-first rendering when stale data is useful. A failed background refetch can produce isError while data is still available.

const todos = useQuery({ queryKey: ['todos'], queryFn: fetchTodos })

if (todos.data)
  return <TodoList todos={todos.data} isRefreshing={todos.isFetching} />
if (todos.isPending) return <Spinner />
if (todos.isError) return <ErrorMessage error={todos.error} />
return null

Use throwOnError when render-time Error Boundaries should own the fallback: