# Watcher 500 Bug
**URL:** https://discuss.elastic.co/t/watcher-500-bug/118281
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [February 2, 2018, 8:51pm UTC](https://discuss.elastic.co/t/watcher-500-bug/118281 "2018-02-02T20:51:40Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@djtecha](https://discuss.elastic.co/u/djtecha)
#### Post date: [February 2, 2018, 8:51pm UTC](https://discuss.elastic.co/t/watcher-500-bug/118281/1 "2018-02-02T20:51:40Z")
So currently if a user saves a watch that is invalid it can break the entire watcher mgmt page in kibana. SHouldn't this just deactivate or prevent the user from saving? I foresee this being a big issue with tracking down broken watches using the backend API to unblock other users.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [February 2, 2018, 8:57pm UTC](https://discuss.elastic.co/t/watcher-500-bug/118281/2 "2018-02-02T20:57:18Z")
Can you elaborate a bit more please?
Invalid how? Break how?
---
### Author:  [@djtecha](https://discuss.elastic.co/u/djtecha)
#### Post date: [February 2, 2018, 9:00pm UTC](https://discuss.elastic.co/t/watcher-500-bug/118281/3 "2018-02-02T21:00:39Z")
Sure. I Created a watch that I had working nicely, then removed the "text" line from the notify-slack block because the 'title' field in the dynamic\_attachments block handled my format the way I wanted it to. I then saved the watch. Following this I tried to click the link for watches in the mgmt page of kibana and was met with a 500 error. In order to fix this I had to use the PUT API to re-add that line. But I can't ensure all my devs will be able to write a perfect JSON object so I foresee this happening again.
---
### Author:  [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [February 7, 2018, 1:58pm UTC](https://discuss.elastic.co/t/watcher-500-bug/118281/4 "2018-02-07T13:58:49Z")
Hi @djtecha,
Yes, we're aware of this issue and actively working on a solution.
Thanks,
Chris
---
### Author:  [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [February 7, 2018, 2:04pm UTC](https://discuss.elastic.co/t/watcher-500-bug/118281/5 "2018-02-07T14:04:13Z")
Actually, @djtecha, if possible, upgrade to 6.2 and see if it still happens there.
---
### Author:  [@djtecha](https://discuss.elastic.co/u/djtecha)
#### Post date: [February 7, 2018, 10:36pm UTC](https://discuss.elastic.co/t/watcher-500-bug/118281/6 "2018-02-07T22:36:03Z")
Sure, tried it on 6.2 today and it still breaks watcher just with a different error now upon saving:
Watcher: Error 400 : json argument must contain an actionJson.slack.message.text property
---
### Author:  [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [February 8, 2018, 2:16pm UTC](https://discuss.elastic.co/t/watcher-500-bug/118281/7 "2018-02-08T14:16:52Z")
Okay cool that's expected. Right now, the only way to fix is by doing what you said, but we're actively working on fixing this.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 8, 2018, 2:17pm UTC](https://discuss.elastic.co/t/watcher-500-bug/118281/8 "2018-03-08T14:17:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.