# \[search-telemetry:search-telemetry\]: version conflict, **URL:** \ **Category:** Kibana\ **Created:** [March 12, 2021, 4:44pm UTC](https://discuss.elastic.co/t/search-telemetry-search-telemetry-version-conflict/267111 "2021-03-12T16:44:20Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![valleram](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/valleram/32/48248_2.png) [@valleram](https://discuss.elastic.co/u/valleram)\ **Post date:** [March 12, 2021, 4:44pm UTC](https://discuss.elastic.co/t/search-telemetry-search-telemetry-version-conflict/267111/1 "2021-03-12T16:44:20Z")
Hi All, I'm receiving a bunch of following errors on Kibana logs, Do you know what could be the reason/solution for them? My Kibana instance is up and running but I'm receiving those errors Any help would be much appreciate it Kibana Logs: ``` {"type":"log","@timestamp":"2021-03-12T09:11:22Z","tags":["error","elasticsearch","data"],"pid":611560,"message":"[version_conflict_engine_exception]: [search-telemetry:search-telemetry]: version conflict, required seqNo [65743002], primary term [8]. current document has seqNo [65743003] and primary term [8]"} {"type":"log","@timestamp":"2021-03-12T09:11:25Z","tags":["error","elasticsearch","data"],"pid":611560,"message":"[version_conflict_engine_exception]: [search-telemetry:search-telemetry]: version conflict, required seqNo [65743050], primary term [8]. current document has seqNo [65743051] and primary term [8]"} {"type":"log","@timestamp":"2021-03-12T09:11:27Z","tags":["error","elasticsearch","data"],"pid":611560,"message":"[version_conflict_engine_exception]: [search-telemetry:search-telemetry]: version conflict, required seqNo [65743105], primary term [8]. current document has seqNo [65743106] and primary term [8]"} ``` ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [March 12, 2021, 4:52pm UTC](https://discuss.elastic.co/t/search-telemetry-search-telemetry-version-conflict/267111/2 "2021-03-12T16:52:05Z")
> [@valleram](#): > > `version_conflict_engine_exception]: [search-telemetry:search` I think, You should be able to safely ignore this issue. There's a bug in how these tasks are handled that's being addressed as part of the resolution for [this issue](https://github.com/elastic/kibana/issues/42055). Effectively, this means the task has already been created and can't be overwritten (which is ok) when you restart Kibana. ...cc @Bamieh should be able to answer/clarify this when he gets a chance. Regards, Rashmi ---
**Author:** ![valleram](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/valleram/32/48248_2.png) [@valleram](https://discuss.elastic.co/u/valleram)\ **Post date:** [March 12, 2021, 5:08pm UTC](https://discuss.elastic.co/t/search-telemetry-search-telemetry-version-conflict/267111/3 "2021-03-12T17:08:03Z")
Thank you @rashmi, Do you know if there is a way to ignore them so that way they would not be shown on Kibana logs? Thank you, Jesus ---
**Author:** ![Bamieh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bamieh/32/38730_2.png) [@Bamieh](https://discuss.elastic.co/u/Bamieh)\ **Post date:** [March 15, 2021, 4:44pm UTC](https://discuss.elastic.co/t/search-telemetry-search-telemetry-version-conflict/267111/4 "2021-03-15T16:44:39Z")
We have a few collectors that run in background tasks every now and then to store data for telemetry/monitoring/beats and some other usecases. The naming here is unfortunate (we should rename them from telemetry to usage/metrics). These tasks or their logs cannot be disabled for now. For the future: We are discussing putting all telemetry/usage logs under a flag to reduce noise in the logs output ---
**Author:** ![rachana\_uday](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rachana_uday/32/86611_2.png) [@rachana\_uday](https://discuss.elastic.co/u/rachana_uday)\ **Post date:** [April 6, 2021, 9:40am UTC](https://discuss.elastic.co/t/search-telemetry-search-telemetry-version-conflict/267111/5 "2021-04-06T09:40:26Z")
I am currently using kibana version 7.10.0 and seeing similar errors in kibana logs > ``` > {"type":"log","@timestamp":"2021-04-06T08:44:44Z","tags":["error","elasticsearch","data"],"pid":22462,"message":"[version_conflict_engine_exception]: [search-telemetry:search-telemetry]: version conflict, required seqNo [2501], primary term [2]. current document has seqNo [2502] and primary term [2]"} > > ``` @Bamieh@rashmi can you please confirm if these errors are expected and can be safely ignored on this version[i.e, 7.10.0] of kibana ?? ---
**Author:** ![Bamieh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bamieh/32/38730_2.png) [@Bamieh](https://discuss.elastic.co/u/Bamieh)\ **Post date:** [April 6, 2021, 3:29pm UTC](https://discuss.elastic.co/t/search-telemetry-search-telemetry-version-conflict/267111/6 "2021-04-06T15:29:23Z")
@rachana_uday Yes this log line can be safely ignored. ---
**Author:** ![rachana\_uday](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rachana_uday/32/86611_2.png) [@rachana\_uday](https://discuss.elastic.co/u/rachana_uday)\ **Post date:** [April 7, 2021, 9:13am UTC](https://discuss.elastic.co/t/search-telemetry-search-telemetry-version-conflict/267111/7 "2021-04-07T09:13:49Z")
@Bamieh would this log be fixed anytime soon? if yes, can you provide the details of which version it might be fixed and when? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 5, 2021, 9:13am UTC](https://discuss.elastic.co/t/search-telemetry-search-telemetry-version-conflict/267111/8 "2021-05-05T09:13:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.