# Error Scheduling Telemetry task

**URL:** <https://discuss.elastic.co/t/error-scheduling-telemetry-task/207002>\
**Category:** Kibana\
**Created:** [November 7, 2019, 7:43pm UTC](https://discuss.elastic.co/t/error-scheduling-telemetry-task/207002 "2019-11-07T19:43:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mehak\_Bhargava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehak_bhargava/32/54750_2.png) [@Mehak\_Bhargava](https://discuss.elastic.co/u/Mehak_Bhargava)\
**Post date:** [November 7, 2019, 7:43pm UTC](https://discuss.elastic.co/t/error-scheduling-telemetry-task/207002/1 "2019-11-07T19:43:10Z")

</div>

I am not able to find the issue with this error and how to understand whats happening! Please help.

```auto
log [19:35:49.863] [info][listening] Server running at http://localhost:5601
  log [19:35:49.878] [info][server][Kibana][http] http server running at http://localhost:5601
  log [19:35:49.890] [warning][telemetry] Error scheduling task, received [task:oss_telemetry-vis_telemetry]: version conflict, document already exists (current version [7]): [version_conflict_engine_exception] [task:oss_telemetry-vis_telemetry]: version conflict, document already exists (current version [7]), with { index_uuid="vpLXqEc_QlOXhqnPG1bOeQ" & shard="0" & index=".kibana_task_manager_1" }
  log [19:35:49.891] [warning][maps] Error scheduling telemetry task, received [task:Maps-maps_telemetry]: version conflict, document already exists (current version [33]): [version_conflict_engine_exception] [task:Maps-maps_telemetry]: version conflict, document already exists (current version [33]), with { index_uuid="vpLXqEc_QlOXhqnPG1bOeQ" & shard="0" & index=".kibana_task_manager_1" }
  log [19:35:49.892] [info][status][plugin:spaces@7.4.0] Status changed from yellow to green - Ready

```

---

<div class="post-metadata">

**Author:** ![Aaron\_Caldwell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aaron_caldwell/32/45755_2.png) [@Aaron\_Caldwell](https://discuss.elastic.co/u/Aaron_Caldwell)\
**Post date:** [November 7, 2019, 7:55pm UTC](https://discuss.elastic.co/t/error-scheduling-telemetry-task/207002/2 "2019-11-07T19:55:58Z")

</div>

Hello Mehak,

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.

Regards,  
Aaron

---

<div class="post-metadata">

**Author:** ![Mehak\_Bhargava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehak_bhargava/32/54750_2.png) [@Mehak\_Bhargava](https://discuss.elastic.co/u/Mehak_Bhargava)\
**Post date:** [November 7, 2019, 8:01pm UTC](https://discuss.elastic.co/t/error-scheduling-telemetry-task/207002/3 "2019-11-07T20:01:31Z")

</div>

Hi @Aaron_Caldwell ,

Thanks for addressing it! If this is safely running, then why is it stopped after the last log line posted above? And I tried this command on Kibana dev tools console, and got no new indices for today-

GET \_cat/indices?h=h,i,s,id,p,r,dc,dd,ss,creation.date.string

```auto
green .monitoring-es-7-2019.10.31 open PIKMApu2QOWOSWn_yjO20Q 1 0 28241 11 11mb 2019-10-31T17:25:18.847Z
yellow test open sFvvHkvpRBC_NWvykeTVCw 1 1 2 0 6.8kb 2019-10-31T00:09:48.083Z
green .monitoring-es-7-2019.11.02 open 6tVXtZALRYmPea8IT2DvPw 1 0 101916 95475 43.4mb 2019-11-02T00:00:07.793Z
green .monitoring-es-7-2019.11.03 open FpeV7FMySXWsEKnSydsTTg 1 0 155532 146829 84.6mb 2019-11-03T00:00:01.578Z
green .monitoring-es-7-2019.11.01 open ld8_s9p8QuyPhhHoUSyTRg 1 0 43604 40443 19.4mb 2019-11-01T00:00:01.308Z
green .apm-agent-configuration open sIAf3LdXRHCmHBQFrncHpw 1 0 0 0 283b 2019-10-17T21:05:01.836Z
yellow logstash-2019.10.30-000001 open WnnV21usSDqM18yvaVowZQ 1 1 1 0 37.3kb 2019-10-30T19:03:01.644Z
green .monitoring-es-7-2019.11.04 open hJZo5XAARLG4EC4zdx9fqg 1 0 139676 132620 75.9mb 2019-11-04T00:00:06.286Z
green .kibana_1 open 74Xfq2xgQxKnxC1XBiyFWg 1 0 18 4 96.1kb 2019-10-17T21:05:05.157Z
green .kibana_task_manager_1 open vpLXqEc_QlOXhqnPG1bOeQ 1 0 2 0 12.6kb 2019-10-17T21:05:05.082Z
yellow mehak open N6ttCpigRuG6RRMH3kpD3g 1 1 0 0 283b 2019-10-30T20:09:08.123Z
green .monitoring-kibana-7-2019.10.31 open _YlOEMh6RvW-YuEAEJDZMA 1 0 2334 0 821.2kb 2019-10-31T17:25:18.475Z
green .monitoring-kibana-7-2019.11.01 open c4Gx85ndRSubX-mBN7GMHA 1 0 3112 0 1mb 2019-11-01T00:00:08.903Z
green .monitoring-kibana-7-2019.11.02 open ZS9UUo94S3i-ZTjq8chSHg 1 0 6369 0 1.9mb 2019-11-02T00:00:04.945Z
green .monitoring-kibana-7-2019.11.03 open EJketYbwTASpH3SurJe3PA 1 0 8638 0 2.6mb 2019-11-03T00:00:09.314Z
green .monitoring-kibana-7-2019.11.04 open tNDxLo2BRD6IIRtgGvqTKQ 1 0 6982 0 2.1mb 2019-11-04T00:00:03.903Z

```

Thanks!

---

<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:** [December 5, 2019, 8:01pm UTC](https://discuss.elastic.co/t/error-scheduling-telemetry-task/207002/4 "2019-12-05T20:01:37Z")

</div>

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