# Nest 6.x GetAsync sets IsValid=false for 404 response

**URL:** <https://discuss.elastic.co/t/nest-6-x-getasync-sets-isvalid-false-for-404-response/178688>\
**Category:** Elasticsearch\
**Created:** [April 26, 2019, 4:08pm UTC](https://discuss.elastic.co/t/nest-6-x-getasync-sets-isvalid-false-for-404-response/178688 "2019-04-26T16:08:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![keithpeck](https://avatars.discourse-cdn.com/v4/letter/k/a3d4f5/32.png) [@keithpeck](https://discuss.elastic.co/u/keithpeck)\
**Post date:** [April 26, 2019, 4:08pm UTC](https://discuss.elastic.co/t/nest-6-x-getasync-sets-isvalid-false-for-404-response/178688/1 "2019-04-26T16:08:51Z")

</div>

We are updating from Nest and ElasticSearch 5.6 to 6.6 and have found that GetAsync sets IsValid=false when the document is not found. This is change from 5.6 where IsValid=true and Found=false. This is on .NET Core.

I can't find any information stating this change. And can't see how the exception could be used to infer it's valid but not found as it is simply an ElasticSearchClientException. Please advise if this is expected behaviour.

---

<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:** [May 24, 2019, 4:08pm UTC](https://discuss.elastic.co/t/nest-6-x-getasync-sets-isvalid-false-for-404-response/178688/2 "2019-05-24T16:08:52Z")

</div>

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