# Balances are updated with a long delay

**URL:** <https://community.bitquery.io/t/balances-are-updated-with-a-long-delay/1838>\
**Category:** GraphQL API\
**Created:** [March 4, 2024, 1:00am UTC](https://community.bitquery.io/t/balances-are-updated-with-a-long-delay/1838 "2024-03-04T01:00:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![roma1901](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@roma1901](https://community.bitquery.io/u/roma1901)\
**Post date:** [March 4, 2024, 1:00am UTC](https://community.bitquery.io/t/balances-are-updated-with-a-long-delay/1838/1 "2024-03-04T01:00:13Z")

</div>

Hi BitQuery community.

After the token swap I checked the balances in the blockchain explorer, but the data sent by Bitquery GraphQL API v1 is still not updated. They take a very long time to update, approximately 3-5 minutes.  
But if I use GraphQL API v2 with the `dataset: realtime` parameter, the data immediately comes back correct.  
It seems to me that by default GraphQL API v1 sends archived data.  
How can I force it to ignore the cache and take only actual data from the blockchain or something like `dataset` parameter in v2

P.S. I can’t use v2, because there are not enough supported networks

For v1 i use the query:

```auto
ethereum(network: $network) {
            address(address: {is: $address}) {
                  address
                  balances {
                        currency {
                              address
                              symbol
                              name
                              decimals
                        }
                        value
                  }
                  balance(in: USDT)
            }
        }

```

---

<div class="post-metadata">

**Author:** ![Divya](https://avatars.discourse-cdn.com/v4/letter/d/13edae/32.png) [@Divya](https://community.bitquery.io/u/Divya)\
**Post date:** [March 4, 2024, 12:22pm UTC](https://community.bitquery.io/t/balances-are-updated-with-a-long-delay/1838/2 "2024-03-04T12:22:36Z")

</div>

Please share the parameters as well. As for delay in v1 APIs, check [Bitquery - System Status](https://account.bitquery.io/user/system_status) for any delays for all chains.

---

<div class="post-metadata">

**Author:** ![roma1901](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@roma1901](https://community.bitquery.io/u/roma1901)\
**Post date:** [March 4, 2024, 12:38pm UTC](https://community.bitquery.io/t/balances-are-updated-with-a-long-delay/1838/3 "2024-03-04T12:38:31Z")

</div>

> [@Divya](#):
>
> Please share the parameters as well. As for delay in v1 APIs, check Bitquery - System Status for any delays for all chains.

```auto
ethereum(network: bsc) {
            address(address: {is: "0xbc29B0935C71865Aa859D9f3cBbA76892298b237"}) {
                  address
                  balances {
                        currency {
                              address
                              symbol
                              name
                              decimals
                        }
                        value
                  }
                  balance(in: USDT)
            }
        }

```

Is it possible to avoid delay in API v1?

---

<div class="post-metadata">

**Author:** ![Divya](https://avatars.discourse-cdn.com/v4/letter/d/13edae/32.png) [@Divya](https://community.bitquery.io/u/Divya)\
**Post date:** [March 5, 2024, 5:00am UTC](https://community.bitquery.io/t/balances-are-updated-with-a-long-delay/1838/4 "2024-03-05T05:00:18Z")

</div>

Use V2 for 0 delays. V1 does have delays. We will move all chains from v1 to v2 soon.

---

<div class="post-metadata">

**Author:** ![roma1901](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@roma1901](https://community.bitquery.io/u/roma1901)\
**Post date:** [March 5, 2024, 8:20am UTC](https://community.bitquery.io/t/balances-are-updated-with-a-long-delay/1838/5 "2024-03-05T08:20:00Z")

</div>

Divya, thanks for answering!