# Watcher is firing twice for the same watch

**URL:** <https://discuss.elastic.co/t/watcher-is-firing-twice-for-the-same-watch/122111>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [March 1, 2018, 3:27pm UTC](https://discuss.elastic.co/t/watcher-is-firing-twice-for-the-same-watch/122111 "2018-03-01T15:27:41Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Maxime\_Poirier-Journ](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@Maxime\_Poirier-Journ](https://discuss.elastic.co/u/Maxime_Poirier-Journ)\
**Post date:** [March 1, 2018, 3:27pm UTC](https://discuss.elastic.co/t/watcher-is-firing-twice-for-the-same-watch/122111/1 "2018-03-01T15:27:41Z")

</div>

Hi there,

I have 1 or 2 watchers that I'm having issues with right now. It is set to trigger once every 30 minutes with a time range of now-30m. For some reason, they are firing twice and I have no idea why. At first i thought i duplicated the watchers so I copied my watch somewhere deleted the watch ID everywhere i could see it. Created a new one and it worked!!!....................... for couples of days maybe 2. It's firing twice again... Can you help me figure out what is going on...

Looks pretty similar to this topic but there is no solution, I tried to take a look at the watch history but I'm not sure what to look for :

> [@X-Pack 6.1.2 - Watcher Firing twice for the same event](https://discuss.elastic.co/t/x-pack-6-1-2-watcher-firing-twice-for-the-same-event/116267):
>
> Hi, For most of our watches, watcher is firing twice for the same results since 6.1.2. Additionally, sometimes it doesn't fire all together. No issues whatsoever on 6.1.1. Anyone know if this is a known bug? Thanks! James

---

<div class="post-metadata">

**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\
**Post date:** [March 1, 2018, 3:43pm UTC](https://discuss.elastic.co/t/watcher-is-firing-twice-for-the-same-watch/122111/2 "2018-03-01T15:43:01Z")

</div>

Hey @Maxime_Poirier-Journ,

This pained me for quite a while. I recreated the problematic watches a few times, to no avail. It eventually stopped duplicating after a few cluster restarts during updates... (currently on 6.2.2). Nothing else I tried worked, and elastic support couldn't replicate the issue.

Sorry I couldn't be of more help!  
James

---

<div class="post-metadata">

**Author:** ![Maxime\_Poirier-Journ](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@Maxime\_Poirier-Journ](https://discuss.elastic.co/u/Maxime_Poirier-Journ)\
**Post date:** [March 1, 2018, 5:24pm UTC](https://discuss.elastic.co/t/watcher-is-firing-twice-for-the-same-watch/122111/3 "2018-03-01T17:24:01Z")

</div>

@jamesspi Interesting 🤔 our clusters are "rotating/updating" as well . Could this be the issue 😮 I will wait until updates are done and report back thank you for your time 🙂

---

<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:** [March 1, 2018, 11:00pm UTC](https://discuss.elastic.co/t/watcher-is-firing-twice-for-the-same-watch/122111/4 "2018-03-01T23:00:34Z")

</div>

Hey,

I highly advise to update to the latest 6.x.y release, as we fixed a number of issues around that in there. We kept the wrong state around for cluster state updates, which could fail to trigger a proper reload of the scheduled watches on one node.

--Alex

---

<div class="post-metadata">

**Author:** ![Maxime\_Poirier-Journ](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@Maxime\_Poirier-Journ](https://discuss.elastic.co/u/Maxime_Poirier-Journ)\
**Post date:** [March 2, 2018, 1:46pm UTC](https://discuss.elastic.co/t/watcher-is-firing-twice-for-the-same-watch/122111/5 "2018-03-02T13:46:51Z")

</div>

Hi Alex,

Our version is 6.1, I guess it matches the 6.x.y. I will wait until cluster updates are done.

---

<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:** [March 2, 2018, 2:57pm UTC](https://discuss.elastic.co/t/watcher-is-firing-twice-for-the-same-watch/122111/6 "2018-03-02T14:57:06Z")

</div>

sorry for not being clear on my end, you should upgrade to 6.2.2.

---

<div class="post-metadata">

**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\
**Post date:** [March 5, 2018, 9:47am UTC](https://discuss.elastic.co/t/watcher-is-firing-twice-for-the-same-watch/122111/7 "2018-03-05T09:47:25Z")

</div>

Thanks @spinscale! I was told this wasn't a bug, but assumed something was done in 6.2.2 anyway 🙂

---

<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:** [April 2, 2018, 9:47am UTC](https://discuss.elastic.co/t/watcher-is-firing-twice-for-the-same-watch/122111/8 "2018-04-02T09:47:44Z")

</div>

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