--- id: useSuspenseInfiniteQuery title: useSuspenseInfiniteQuery redirect_from: - framework/react/reference/useSuspenseInfiniteQuery --- ```ts function useSuspenseInfiniteQuery(options, queryClient?): UseSuspenseInfiniteQueryResult; ``` Defined in: [packages/react-query/src/useSuspenseInfiniteQuery.ts:104](https://github.com/TanStack/query/blob/main/packages/react-query/src/useSuspenseInfiniteQuery.ts#L104) The options for `useSuspenseInfiniteQuery` are the same as for `useInfiniteQuery`, except for `throwOnError`, `enabled`, and `placeholderData`. Caveat: cancellation does not work. ## Type Parameters ### TQueryFnData `TQueryFnData` ### TError `TError` = `Error` ### TData `TData` = [`InfiniteData`](../interfaces/InfiniteData.md)\<`TQueryFnData`, `unknown`\> ### TQueryKey `TQueryKey` *extends* readonly `unknown`[] = readonly `unknown`[] ### TPageParam `TPageParam` = `unknown` ## Parameters ### options [`UseSuspenseInfiniteQueryOptions`](../interfaces/UseSuspenseInfiniteQueryOptions.md)\<`TQueryFnData`, `TError`, `TData`, `TQueryKey`, `TPageParam`\> The [UseSuspenseInfiniteQueryOptions](../interfaces/UseSuspenseInfiniteQueryOptions.md) to use — the same options as `useInfiniteQuery`, minus the ones listed above. ### queryClient? [`QueryClient`](../classes/QueryClient.md) Use this to use a custom `QueryClient`. Otherwise, the one from the nearest context will be used. ## Returns [`UseSuspenseInfiniteQueryResult`](../type-aliases/UseSuspenseInfiniteQueryResult.md)\<`TData`, `TError`\> The same object as `useInfiniteQuery`, except that `data` is guaranteed to be defined, `isPlaceholderData` is missing, and `status` is either `success` or `error` (with the derived flags set accordingly). ## Remarks Multiple suspenseful query calls in the same component suspend serially, causing a request waterfall — each one blocks rendering until it resolves, so the next doesn't even start fetching until then. There's no way to parallelize multiple infinite queries under Suspense. Also keep in mind that imperative fetch calls, such as `fetchNextPage`, may interfere with the default refetch behavior, resulting in outdated data. Make sure to call these functions only in response to user actions, or add conditions like `hasNextPage && !isFetching`. ## See [useInfiniteQuery](useInfiniteQuery.md) for the non-Suspense version of this hook. ## Example The query error is thrown if a fetch fails and no cached data exists yet, so an error boundary is required around ``. A failed background refetch instead continues to render the cached data. Use [QueryErrorResetBoundary](QueryErrorResetBoundary.md) to let the user retry after such an error: ```tsx import { Suspense } from 'react' import { ErrorBoundary } from 'react-error-boundary' import { QueryErrorResetBoundary, useSuspenseInfiniteQuery, } from '@tanstack/react-query' function Projects() { // `data` is guaranteed to be defined here — no `isPending` check needed. const { data, fetchNextPage, hasNextPage, isFetching, isFetchingNextPage } = useSuspenseInfiniteQuery({ queryKey: ['projects'], queryFn: ({ pageParam }) => fetchProjects(pageParam), initialPageParam: 0, getNextPageParam: (lastPage) => lastPage.nextId, }) return (
    {data.pages.map((page) => page.projects.map((project) =>
  • {project.name}
  • ), )}
) } function App() { return ( {({ reset }) => ( (
There was an error!
)} > Loading projects...}>
)}
) } ```