# Why update or create operation could be failed?

**URL:** <https://discuss.elastic.co/t/why-update-or-create-operation-could-be-failed/118248>\
**Category:** Elasticsearch\
**Created:** [February 2, 2018, 3:42pm UTC](https://discuss.elastic.co/t/why-update-or-create-operation-could-be-failed/118248 "2018-02-02T15:42:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kozlone](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kozlone](https://discuss.elastic.co/u/kozlone)\
**Post date:** [February 2, 2018, 3:42pm UTC](https://discuss.elastic.co/t/why-update-or-create-operation-could-be-failed/118248/1 "2018-02-02T15:42:26Z")

</div>

Hi, long story short: I need to implement a kind of rollback feature and I'm interested in what reasons could be which causes update/create operations failure. I'm using Elasticsearch with Python. When the update operation executions ends-up it returns a list of dictionaries with values of doc id, operation type and status. So, what could happen to cause the status be failed. If there is a conflict than an appropriate exception will be raised.

---

<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:** [March 2, 2018, 3:42pm UTC](https://discuss.elastic.co/t/why-update-or-create-operation-could-be-failed/118248/2 "2018-03-02T15:42:37Z")

</div>

Closed on March 2, 2018, 3:42pm UTC

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