# Gateway Should Be Responsible For Making Sure Query Results Are Consistent Without Specifying Block

**URL:** <https://forum.thegraph.com/t/gateway-should-be-responsible-for-making-sure-query-results-are-consistent-without-specifying-block/2483>\
**Category:** Questions & Feedback\
**Created:** [September 1, 2021, 1:52am UTC](https://forum.thegraph.com/t/gateway-should-be-responsible-for-making-sure-query-results-are-consistent-without-specifying-block/2483 "2021-09-01T01:52:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![benyo](https://avatars.discourse-cdn.com/v4/letter/b/7bcc69/32.png) [@benyo](https://forum.thegraph.com/u/benyo)\
**Post date:** [September 1, 2021, 1:52am UTC](https://forum.thegraph.com/t/gateway-should-be-responsible-for-making-sure-query-results-are-consistent-without-specifying-block/2483/1 "2021-09-01T01:52:43Z")

</div>

When querying for latest entities from a subgraph, one is not ensured a consistent response without specifying a block number or hash. This makes using this type of query that depends on up-to-date data at each block much more cumbersome, requiring the client to fetch the latest block number/hash from somewhere before sending off the query. Considering that polling for the latest data from a subgraph is likely a common use case, I believe the gateway itself should be responsible for populating the latest block number if no block is provided in the query.