# 409 Conflict on update\_by\_query consecutive calls

**URL:** <https://discuss.elastic.co/t/409-conflict-on-update-by-query-consecutive-calls/130667>\
**Category:** Elasticsearch\
**Created:** [May 4, 2018, 5:03pm UTC](https://discuss.elastic.co/t/409-conflict-on-update-by-query-consecutive-calls/130667 "2018-05-04T17:03:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anton\_Garakh](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@Anton\_Garakh](https://discuss.elastic.co/u/Anton_Garakh)\
**Post date:** [May 4, 2018, 5:03pm UTC](https://discuss.elastic.co/t/409-conflict-on-update-by-query-consecutive-calls/130667/1 "2018-05-04T17:03:20Z")

</div>

Hi guys

Came to the point where I can't solve the problem myself..

I have to update big enough amount of documents and I have to do it in cycle. That's the reason why I have to perform consecutive update\_by\_query requests. What these requests do is appending element to array inside a document. And at some point it responds with 409 conflict. Like I understand the problem is that after adding new element to the inner array in the document in the next iteration it tries to update the same document and elastic doesn't see the updated version, instead tries to update the document with not legal version.

The question is how to handle this situation so that conflicts don't appear?

---

<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:** [June 1, 2018, 5:03pm UTC](https://discuss.elastic.co/t/409-conflict-on-update-by-query-consecutive-calls/130667/2 "2018-06-01T17:03:21Z")

</div>

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