# useMutation refetching stale data?

**URL:** https://community.apollographql.com/t/usemutation-refetching-stale-data/7029
**Category:** Client SDKs
**Tags:** client
**Created:** [December 7, 2023, 2:42am UTC](https://community.apollographql.com/t/usemutation-refetching-stale-data/7029 "2023-12-07T02:42:44Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![alec](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/alec/32/4790_2.png) [@alec](https://community.apollographql.com/u/alec)
#### Post date: [December 7, 2023, 2:42am UTC](https://community.apollographql.com/t/usemutation-refetching-stale-data/7029/1 "2023-12-07T02:42:44Z")

</div>

When a user triggers a mutation multiple times in succession, I can get stale data from the refetched queries.

I have something like this, using ‘active’ to refetch the data on the screen:

```javascript
  const [removeItem] = useMutation(REMOVE_ITEM, {
    refetchQueries: "active",
  });

```

But, refetching the items query can take a few seconds.

If removeItem is called a few times in quick succession, for example, the refetch will return an items list that only has the first of the items removed, rather than all of them.

Should this be the case?

I’ve been looking into trying to cancel previous refetch requests with AbortController, but it’s a bit wonky.

Thanks

---

<div class="post-metadata">

### Author: ![Justin\_Gonzalez](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/justin_gonzalez/32/5359_2.png) [@Justin\_Gonzalez](https://community.apollographql.com/u/Justin_Gonzalez)
#### Post date: [February 6, 2025, 8:47pm UTC](https://community.apollographql.com/t/usemutation-refetching-stale-data/7029/2 "2025-02-06T20:47:52Z")

</div>