Watch does not exist – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when you’re trying to access or manipulate a watch in Elasticsearch that doesn’t exist. Watches are part of the alerting feature in Elasticsearch and are used to automatically check data and send alerts. To resolve this issue, you can either create a new watch with the specified ID or check if the ID of the existing watch is correct. Also, ensure that the watch is not deleted or moved to another cluster. Lastly, check your permissions, as you might not have the necessary rights to access the watch.

This guide will help you check for common problems that cause the log ” watch [{}] does not exist ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “watch [{}] does not exist” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else {
 try {
 ctx.ensureWatchExists(() -> {
 GetResponse resp = getWatch(watchId);
 if (resp.isExists() == false) {
 throw new ResourceNotFoundException("watch [{}] does not exist"; watchId);
 return parser.parseWithSecrets(


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?