I have a poorly designed architecture we are currently hitting a limit with. Without going into unecessary detail, we are having to use fetchMore to get some additional data. My understanding is that the following: const { data: commentsData, fetchMore: fetchMoreComments } = useQuery(SEARCH_COMME…

whenever the server responds with a nextToken React knows to call the fetchMore again. You did not include any code for this part (calling fetchMore), could you please add that as well?

[Screen Shot 2023-02-24 at 7.59.32 AM] Thanks @lenz my train of thought rolled right on by this most important aspect.

Hi there, I’m sorry for the late reply. For me, your merge function looks suspicious - it seems to change the shape of the query somehow, so it should probably either be return [...existing, ...incoming], or { ...existing, ...incoming, items: [...existing.items, ...incoming.items] }. Generally, it …

Updating fetchMore data in cache does not trigger useEffect

Client SDKs

Endlessline February 24, 2023, 4:00pm 3

Thanks @lenz my train of thought rolled right on by this most important aspect.

FetchMore no re-render?

Topic		Replies	Views
FetchMore no re-render? Client SDKs client , web	1	948	February 26, 2023
Use cached pagination data if query has already been requested before? Client SDKs client , caching	2	97	October 8, 2025
Can I Use Reactive Variables Instead of fetchMore() and refetchQueries()? Client SDKs client	16	134	June 27, 2025
Trouble with `useQuery` - 'cache-only' not receiving updates? Client SDKs client , web	3	803	February 6, 2025
startTransition with fetchMore (merge data) return incoming for a sec first then return merged data Client SDKs client , web	1	344	January 11, 2024

Updating fetchMore data in cache does not trigger useEffect

Related topics