# Watcher's State - Error!
**URL:** https://discuss.elastic.co/t/watchers-state-error/119132
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [February 8, 2018, 10:20pm UTC](https://discuss.elastic.co/t/watchers-state-error/119132 "2018-02-08T22:20:51Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@alexus](https://discuss.elastic.co/u/alexus)
#### Post date: [February 8, 2018, 10:20pm UTC](https://discuss.elastic.co/t/watchers-state-error/119132/1 "2018-02-08T22:20:51Z")
I just noticed that several of X-Pack Monitoring watcher's state is:
> Error!
w/ comment
> Execution Failing
Please advise.
---
### Author:  [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)
#### Post date: [February 9, 2018, 9:17pm UTC](https://discuss.elastic.co/t/watchers-state-error/119132/2 "2018-02-09T21:17:37Z")
Hey Alexus, can you tell me what the name of the failing watch is? Thanks.
CJ
---
### Author:  [@alexus](https://discuss.elastic.co/u/alexus)
#### Post date: [February 9, 2018, 9:29pm UTC](https://discuss.elastic.co/t/watchers-state-error/119132/3 "2018-02-09T21:29:49Z")
Error:
- X-Pack Monitoring: Cluster Status
- X-Pack Monitoring: Nodes Changed
- X-Pack Monitoring: Kibana Version Mismatch
- X-Pack Monitoring: Logstash Version Mismatch
OK:
- X-Pack Monitoring: Elasticsearch Version Mismatch
- X-Pack Monitoring: License Expiration
* * *
I also created several other "watch", one executes without any issues and rest shows blank in "Last Triggered"
---
### Author:  [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)
#### Post date: [February 9, 2018, 10:04pm UTC](https://discuss.elastic.co/t/watchers-state-error/119132/4 "2018-02-09T22:04:53Z")
OK, so one of the watches which is failing is the `elasticsearch_cluster_status` watch. Could you execute this watch and share the output with me? You can run the watch like this:
```auto
POST /_xpack/watcher/watch/${cluster_uuid}_elasticsearch_cluster_status/_execute
```
The UUID should be visible in the Watches table, or you can get it from the `_id` value of the response from `GET /.watches/_search?_source=_id`.
Thanks,
CJ
---
### Author:  [@alexus](https://discuss.elastic.co/u/alexus)
#### Post date: [February 9, 2018, 10:38pm UTC](https://discuss.elastic.co/t/watchers-state-error/119132/5 "2018-02-09T22:38:27Z")
@cjcenizal pretty sure I wouldn't be able to paste my answer here, so I [pastebin](https://pastebin.com/EpbSxQV7) it instead)
---
### Author:  [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)
#### Post date: [February 9, 2018, 10:42pm UTC](https://discuss.elastic.co/t/watchers-state-error/119132/6 "2018-02-09T22:42:58Z")
Well, that's odd. That looks like a healthy watch. Could you share a screenshot of your watches table, showing the failed watches?
---
### Author:  [@alexus](https://discuss.elastic.co/u/alexus)
#### Post date: [February 10, 2018, 4:09am UTC](https://discuss.elastic.co/t/watchers-state-error/119132/7 "2018-02-10T04:09:24Z")
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [February 12, 2018, 8:58am UTC](https://discuss.elastic.co/t/watchers-state-error/119132/8 "2018-02-12T08:58:57Z")
some moon shot from the current information: do you have an email account configured in your alerting setup, that maybe is not set up properly?
--Alex
---
### Author:  [@alexus](https://discuss.elastic.co/u/alexus)
#### Post date: [February 13, 2018, 4:04am UTC](https://discuss.elastic.co/t/watchers-state-error/119132/9 "2018-02-13T04:04:29Z")
for moon shot... it's like bullseyes)
my setup is testing environment, I'll try to configure email account and see if that resolves my issue...
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [February 13, 2018, 9:46am UTC](https://discuss.elastic.co/t/watchers-state-error/119132/10 "2018-02-13T09:46:57Z")
would it be also possible to share the output of the watcher history for one of your watches where the run was failed?
Thanks a lot!
---
### Author:  [@alexus](https://discuss.elastic.co/u/alexus)
#### Post date: [February 13, 2018, 5:50pm UTC](https://discuss.elastic.co/t/watchers-state-error/119132/11 "2018-02-13T17:50:53Z")
@spinscale, can you provide curl command?
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [February 14, 2018, 7:36am UTC](https://discuss.elastic.co/t/watchers-state-error/119132/12 "2018-02-14T07:36:55Z")
If you only have the monitoring watches installed, you can just run this
```auto
GET .watcher-history-*/_search
{
"sort": [
{
"result.execution_time": {
"order": "desc"
}
}
]
}
```
might be too much output to put here, so please put it into a gist/pastebin or something.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 14, 2018, 7:37am UTC](https://discuss.elastic.co/t/watchers-state-error/119132/13 "2018-03-14T07:37:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.