# Getting the final query result after repeatedly calling fetchMore

**URL:** <https://community.apollographql.com/t/getting-the-final-query-result-after-repeatedly-calling-fetchmore/3532>\
**Category:** Client SDKs\
**Tags:** client, web\
**Created:** [May 17, 2022, 8:37pm UTC](https://community.apollographql.com/t/getting-the-final-query-result-after-repeatedly-calling-fetchmore/3532 "2022-05-17T20:37:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![benashby](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/benashby/32/2045_2.png) [@benashby](https://community.apollographql.com/u/benashby)\
**Post date:** [May 17, 2022, 8:37pm UTC](https://community.apollographql.com/t/getting-the-final-query-result-after-repeatedly-calling-fetchmore/3532/1 "2022-05-17T20:37:06Z")

</div>

What’s the most straightforward way to get access to the fully merged result set with all pages, after repeatedly calling fetchMore to “exhaust” a paginated query? I’m currently using reobserveCacheFirst to accomplish this, but it feels bad since this method was just introduce as public API, and I’m worried it may not stick.

---

<div class="post-metadata">

**Author:** ![benashby](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/benashby/32/2045_2.png) [@benashby](https://community.apollographql.com/u/benashby)\
**Post date:** [May 17, 2022, 9:23pm UTC](https://community.apollographql.com/t/getting-the-final-query-result-after-repeatedly-calling-fetchmore/3532/2 "2022-05-17T21:23:53Z")

</div>

Also in this case, I want to get the result from calling fetchMore (i.e. just getting it from the query hook delivering an updated result isn’t enough)