# Watcher: Error 400 Bad Request: json argument must contain a watchStatusJson property

**URL:** https://discuss.elastic.co/t/watcher-error-400-bad-request-json-argument-must-contain-a-watchstatusjson-property/120115
**Category:** Elasticsearch
**Created:** [February 16, 2018, 7:54am UTC](https://discuss.elastic.co/t/watcher-error-400-bad-request-json-argument-must-contain-a-watchstatusjson-property/120115 "2018-02-16T07:54:53Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![rippfx](https://avatars.discourse-cdn.com/v4/letter/r/9f8e36/32.png) [@rippfx](https://discuss.elastic.co/u/rippfx)
#### Post date: [February 20, 2018, 8:51pm UTC](https://discuss.elastic.co/t/watcher-error-400-bad-request-json-argument-must-contain-a-watchstatusjson-property/120115/5 "2018-02-20T20:51:16Z")

</div>

found the solution.

> [@ES 5.4 =\> 6.0 Upgrade. Watcher Issues](https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481):
>
> I have upgrade ES from 5.4 to 6.0, including Kibana and all the plugins we have installed. They are discovery-ec2, repository-s3, and x-pack. I followed the upgrade instructions as listed here: [https://www.elastic.co/guide/en/elasticsearch/reference/6.0/restart-upgrade.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.0/restart-upgrade.html). Everything went well including remapping the Kibana index. The logs for my cluster keep dumping the following though... [WARN][o.e.x.w.WatcherLifeCycleService] [MEEC-x7] not starting watcher, upgrade API run required: .wat…

---

_[View the full topic](https://discuss.elastic.co/t/watcher-error-400-bad-request-json-argument-must-contain-a-watchstatusjson-property/120115)._