# Update\_by\_query/delete\_by\_query conflicts=proceed doesn't actually perform the operation?
**URL:** https://discuss.elastic.co/t/update-by-query-delete-by-query-conflicts-proceed-doesnt-actually-perform-the-operation/255907
**Category:** Elasticsearch
**Created:** [November 18, 2020, 9:56pm UTC](https://discuss.elastic.co/t/update-by-query-delete-by-query-conflicts-proceed-doesnt-actually-perform-the-operation/255907 "2020-11-18T21:56:05Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@redec](https://discuss.elastic.co/u/redec)
#### Post date: [November 18, 2020, 9:56pm UTC](https://discuss.elastic.co/t/update-by-query-delete-by-query-conflicts-proceed-doesnt-actually-perform-the-operation/255907/1 "2020-11-18T21:56:05Z")
I just discovered that _conflicts=proceed_ doesn't mean "proceed with the requested operation when a conflict occurs"...instead it apparently means "just skip doing the requested operation on that document". I really wish the docs were clearer on that cuz god knows how many bugs I have because of that 😅. At any rate, is there any way to get it to actually perform the operation, regardless of if there's a conflict?....like....I'm trying to delete a document, I don't really care what modifications may have happened to it, I know I want to delete it now. Same with the update-by-query, if I want to selectively update a field on the document I don't really care that other fields may have changed on the doc since it was indexed.
I understand there are cases where the modifications _do_ matter...where the conflicting modifications could make the document no longer match the query on update\_by\_query/delete\_by\_query, but that doesn't apply in my use case...so I'm hoping there's a way to just force the operation to go through...
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [November 18, 2020, 10:28pm UTC](https://discuss.elastic.co/t/update-by-query-delete-by-query-conflicts-proceed-doesnt-actually-perform-the-operation/255907/2 "2020-11-18T22:28:08Z")
It'd be worth creating an issue on GitHub about this to ask for further clarification to be added 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 16, 2020, 10:28pm UTC](https://discuss.elastic.co/t/update-by-query-delete-by-query-conflicts-proceed-doesnt-actually-perform-the-operation/255907/3 "2020-12-16T22:28:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.