# Results from ES index are null without error

**URL:** <https://discuss.elastic.co/t/results-from-es-index-are-null-without-error/211804>\
**Category:** Elasticsearch\
**Created:** [December 13, 2019, 2:41pm UTC](https://discuss.elastic.co/t/results-from-es-index-are-null-without-error/211804 "2019-12-13T14:41:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbrimmer83](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mbrimmer83/32/52975_2.png) [@mbrimmer83](https://discuss.elastic.co/u/mbrimmer83)\
**Post date:** [December 13, 2019, 2:41pm UTC](https://discuss.elastic.co/t/results-from-es-index-are-null-without-error/211804/1 "2019-12-13T14:41:02Z")

</div>

On ES 7.2 and using Elasticsearch Client for Node JS.

After I delete a document from my ES index, I sometimes have a brief period of time where future queries will return null results so they don't have a body or hits that is empty which is what I would expect if there were no results from the search. I am wondering if anyone has encountered this in the past and if there is something I have setup wrong in my index. I am potentially looking at setting up a retry if this case occurs since it tends to only happen after a delete and for a short period of time.

I am also looking at using wait\_for so the refresh takes place before the response returns from the delete. Could the problem be that I am attempting to fetch new results right after the delete operation occurs and it is busy updating?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 10, 2020, 2:41pm UTC](https://discuss.elastic.co/t/results-from-es-index-are-null-without-error/211804/2 "2020-01-10T14:41:06Z")

</div>

Closed on January 10, 2020, 2:41pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.