Watch with id does not exist – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch tries to access a watch (a set of instructions to routinely run specific searches and actions) with a specific ID, but it cannot find it. This could be due to the watch being deleted or not created yet. To resolve this issue, you can verify the existence of the watch by using the Get Watch API. If it doesn’t exist, you need to create it using the Put Watch API. If it should be there but isn’t, check for issues with your Elasticsearch cluster or data integrity.

This guide will help you check for common problems that cause the log ” Watch with id [{}] 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 with id [{}] does not exist” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 executeWatch(request; listener; watch; true);
 } else {
 listener.onFailure(new ResourceNotFoundException("Watch with id [{}] does not exist"; request.getId()));
 }; listener::onFailure);
 } else if (request.getWatchSource() != null) {