# Error message with query

**URL:** <https://community.bitquery.io/t/error-message-with-query/1093>\
**Category:** GraphQL API\
**Tags:** support, open\
**Created:** [June 18, 2022, 3:53am UTC](https://community.bitquery.io/t/error-message-with-query/1093 "2022-06-18T03:53:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bro](https://avatars.discourse-cdn.com/v4/letter/b/47e85d/32.png) [@Bro](https://community.bitquery.io/u/Bro)\
**Post date:** [June 18, 2022, 3:53am UTC](https://community.bitquery.io/t/error-message-with-query/1093/1 "2022-06-18T03:53:53Z")

</div>

I’ve noticed that sometimes I’ll get an error response from BitQuery that says something about the query taking too long to process, like its timing out.

Then I’ll try the same query again and it’ll work the second time.

What’s the reason for this? Is this normal? How can I prevent this from happening or mitigate the frequency of it?

Thanks

---

<div class="post-metadata">

**Author:** ![sayon-bitquery](https://sea2.discourse-cdn.com/flex016/user_avatar/community.bitquery.io/sayon-bitquery/32/522_2.png) [@sayon-bitquery](https://community.bitquery.io/u/sayon-bitquery)\
**Post date:** [June 18, 2022, 12:15pm UTC](https://community.bitquery.io/t/error-message-with-query/1093/2 "2022-06-18T12:15:03Z")

</div>

In order to mitigate it from happening in the future, it is always recommended to pass an optimized GraphQL query to the IDE. Filtering the query with parameters like _date_, _limit_, _exchangeName_, etc. can help in optimizing your GraphQL query and hence, reduce such errors from happening.