# Elasticsearch NET NEST 6.5.1 API - recoverable errors

**URL:** <https://discuss.elastic.co/t/elasticsearch-net-nest-6-5-1-api-recoverable-errors/173257>\
**Category:** Elasticsearch\
**Created:** [March 21, 2019, 7:35am UTC](https://discuss.elastic.co/t/elasticsearch-net-nest-6-5-1-api-recoverable-errors/173257 "2019-03-21T07:35:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathan1](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@Jonathan1](https://discuss.elastic.co/u/Jonathan1)\
**Post date:** [March 21, 2019, 7:35am UTC](https://discuss.elastic.co/t/elasticsearch-net-nest-6-5-1-api-recoverable-errors/173257/1 "2019-03-21T07:35:21Z")

</div>

Hi

I am using the NEST API 6.5.1.

When indexing data I need to separate the errors for operations that should be automatically retried and the errors for operations that should not be retried. I am using the BulkDescriptor.IndexMany method and the ElasticClient.BulkAsync method. For example:

- If an "Invalid index name" error is returned then the error should be logged but the operation not automatically retried.

- If a network error is return eg a sniffing error then index operation should be retried later when network connection is restored.

Currently I am examining the IBulkResponse.Items collection to determine the error.

I cannot determine a clear way separating the two types of error. Can anyone provide assistance?

Thanks

---

<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:** [April 18, 2019, 7:35am UTC](https://discuss.elastic.co/t/elasticsearch-net-nest-6-5-1-api-recoverable-errors/173257/2 "2019-04-18T07:35:21Z")

</div>

Closed on April 18, 2019, 7:35am UTC

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