# ML alerts triggering on interim result

**URL:** <https://discuss.elastic.co/t/ml-alerts-triggering-on-interim-result/158408>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-machine-learning, elastic-stack-alerting\
**Created:** [November 27, 2018, 7:47pm UTC](https://discuss.elastic.co/t/ml-alerts-triggering-on-interim-result/158408 "2018-11-27T19:47:05Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![richcollier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/richcollier/32/115035_2.png) [@richcollier](https://discuss.elastic.co/u/richcollier)\
**Post date:** [November 29, 2018, 10:14pm UTC](https://discuss.elastic.co/t/ml-alerts-triggering-on-interim-result/158408/5 "2018-11-29T22:14:59Z")

</div>

By the way, I cannot seem to replicate your situation at the moment. Until we figure out what's going on you could work around the situation by modifying the Watch to ignore interim results. Just add a:

```auto
                  { "term" : { "is_interim" : "false"}}

```

to the query the Watch is making.

---

_[View the full topic](https://discuss.elastic.co/t/ml-alerts-triggering-on-interim-result/158408)._