# Watcher UI Broken on slack.message.text property

**URL:** <https://discuss.elastic.co/t/watcher-ui-broken-on-slack-message-text-property/131344>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [May 10, 2018, 7:00pm UTC](https://discuss.elastic.co/t/watcher-ui-broken-on-slack-message-text-property/131344 "2018-05-10T19:00:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MorganRIch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/morganrich/32/28786_2.png) [@MorganRIch](https://discuss.elastic.co/u/MorganRIch)\
**Post date:** [May 10, 2018, 7:00pm UTC](https://discuss.elastic.co/t/watcher-ui-broken-on-slack-message-text-property/131344/1 "2018-05-10T19:00:14Z")

</div>

There's already an existing related ticket for this here - [Make `message.text` not required for Slack action](https://discuss.elastic.co/t/make-message-text-not-required-for-slack-action/120939), but responses are closed and I wanted to get an idea of when or if a fix for this is on the horizon. Right now I can't access the Watcher UI on v6.2.4 because of an error: "Watcher: Error 400 Bad Request: json argument must contain an actionJson.slack.message.text property". My watches have a message.attachments.text, so the additional message.text shouldn't be necessary, and that error shouldn't prevent me from accessing the UI to update the Watcher.

I've attempted updating the watcher via the DevTools, but I have a lot of watches to update and moving around all of the JSON is a bit tedious. I've also tried using \_update\_by\_query, but that doesn't work either because I'm using the Cloud product so I'm unable to set "watcher.index.rest.direct\_access: true" in my elasticsearch.yml.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [May 11, 2018, 6:56am UTC](https://discuss.elastic.co/t/watcher-ui-broken-on-slack-message-text-property/131344/2 "2018-05-11T06:56:17Z")

</div>

hey,

the issue mentioned in another post is public now, see [Watcher UI Broken on slack.message.text property](https://discuss.elastic.co/t/watcher-ui-broken-on-slack-message-text-property/131344)

I do think however, that we should fix the UI regardless of that. I'll ping our watcher UI folks about that.

Sorry for the inconvenience.

--Alex

---

<div class="post-metadata">

**Author:** ![MorganRIch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/morganrich/32/28786_2.png) [@MorganRIch](https://discuss.elastic.co/u/MorganRIch)\
**Post date:** [May 31, 2018, 2:38pm UTC](https://discuss.elastic.co/t/watcher-ui-broken-on-slack-message-text-property/131344/3 "2018-05-31T14:38:58Z")

</div>

I'm not sure if this is fixed, but I ended up regaining access to the Watcher UI by manually updating the JSON for each of the watches. It was a bit tedious, but after adding in the `slack.message.text` property, the Watcher UI started working again.

---

<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:** [June 28, 2018, 2:39pm UTC](https://discuss.elastic.co/t/watcher-ui-broken-on-slack-message-text-property/131344/4 "2018-06-28T14:39:56Z")

</div>

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