# Enable/Disable watches
**URL:** https://discuss.elastic.co/t/enable-disable-watches/27160
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [August 10, 2015, 9:16pm UTC](https://discuss.elastic.co/t/enable-disable-watches/27160 "2015-08-10T21:16:13Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@aochsner](https://discuss.elastic.co/u/aochsner)
#### Post date: [August 10, 2015, 9:16pm UTC](https://discuss.elastic.co/t/enable-disable-watches/27160/1 "2015-08-10T21:16:13Z")
Is there a way to enable/disable watches? Was hoping there might be a special trigger or some way to trick the trigger to not fire but not finding anything.
Any thoughts?
---
### Author:  [@uboness](https://discuss.elastic.co/u/uboness)
#### Post date: [August 10, 2015, 10:12pm UTC](https://discuss.elastic.co/t/enable-disable-watches/27160/2 "2015-08-10T22:12:34Z")
Watcher currently doesn't support enable/disable (though being an essential functionality it's already on the short term roadmap). One way you could consider to simulate "disabling" a watch (albeit hacky) is to change its trigger to a cron trigger that will never fire (a la `0 0 0 1 1 ? 2050`).
---
### Author:  [@aochsner](https://discuss.elastic.co/u/aochsner)
#### Post date: [August 11, 2015, 2:35am UTC](https://discuss.elastic.co/t/enable-disable-watches/27160/3 "2015-08-11T02:35:44Z")
Thanks Uri. That was exactly what I was looking for (not sure how I missed it)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:49pm UTC](https://discuss.elastic.co/t/enable-disable-watches/27160/4 "2017-07-06T13:49:02Z")