Watch with id 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.

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”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

Watch watch = parser.parseWithSecrets(request.getWatchId(); true; getResponse.getSourceAsBytesRef(); now;
 XContentType.JSON; getResponse.getSeqNo(); getResponse.getPrimaryTerm());
 listener.onResponse(new ActivateWatchResponse(watch.status()));
 } else {
 listener.onFailure(new ResourceNotFoundException("Watch with id [{}] does not exist";
 }; listener::onFailure); client::get);
 }; listener::onFailure); client::update);
 } catch (IOException e) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content