# Courier fetch error and conflicting indexes

**URL:** <https://discuss.elastic.co/t/courier-fetch-error-and-conflicting-indexes/47648>\
**Category:** Kibana\
**Created:** [April 18, 2016, 12:17pm UTC](https://discuss.elastic.co/t/courier-fetch-error-and-conflicting-indexes/47648 "2016-04-18T12:17:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sunilmchaudhari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sunilmchaudhari/32/9475_2.png) [@sunilmchaudhari](https://discuss.elastic.co/u/sunilmchaudhari)\
**Post date:** [April 18, 2016, 12:17pm UTC](https://discuss.elastic.co/t/courier-fetch-error-and-conflicting-indexes/47648/1 "2016-04-18T12:17:01Z")

</div>

Hi,  
When it says n shards out of n failed, then how to get failed shards/indexes?

How can we correct those shards?

I have eventLogTime field which is conflicting across indexes? How to get the indexes across which it conflicts?

br,  
Sunil

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 18, 2016, 9:08pm UTC](https://discuss.elastic.co/t/courier-fetch-error-and-conflicting-indexes/47648/2 "2016-04-18T21:08:17Z")

</div>

Check you ES logs, they should mention something that will help.

---

<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:** [July 6, 2017, 1:55pm UTC](https://discuss.elastic.co/t/courier-fetch-error-and-conflicting-indexes/47648/3 "2017-07-06T13:55:44Z")

</div>