Watch does not exist – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

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”classname  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(watchId; true; resp.getSourceAsBytesRef(); ctx.executionTime(); XContentType.JSON;
 resp.getSeqNo(); resp.getPrimaryTerm());
 } catch (ResourceNotFoundException e) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content