# Use cases for queries

**URL:** <https://community.temporal.io/t/use-cases-for-queries/3595>\
**Category:** Community Support\
**Tags:** use-case-validation, performance, best-practices\
**Created:** [December 13, 2021, 12:29pm UTC](https://community.temporal.io/t/use-cases-for-queries/3595 "2021-12-13T12:29:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [December 13, 2021, 2:40pm UTC](https://community.temporal.io/t/use-cases-for-queries/3595/2 "2021-12-13T14:40:16Z")

</div>

There can be many use cases for queries, [this post](https://community.temporal.io/t/signalling-system-human-driven-workflows/160) shows how they could be used in a “human in the loop” scenario.

Uses cases revolve around being able to get/poll the current wf state, doing that with queries is fully consistent (relies on primary temporal db).  
Using visibility queries, for example querying Elasticsearch directly or using ListWorkflowExecutions api is eventually consistent.

---

_[View the full topic](https://community.temporal.io/t/use-cases-for-queries/3595)._