Could not parse condition for watch . – 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 ” could not parse condition for watch . ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “could not parse [{}] condition for watch [{}].”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

while ((token = parser.nextToken()) != XContentParser.Token.END_OBJECT) {
 if (token == XContentParser.Token.FIELD_NAME) {
 if (parser.currentName().equals("value")) {
 token = parser.nextToken();
 if (!op.supportsStructures() && !token.isValue() && token != XContentParser.Token.VALUE_NULL) {
 throw new ElasticsearchParseException("could not parse [{}] condition for watch [{}]. " +
 "compared value for [{}] with operation [{}] must either be a numeric; string; " +
 "boolean or null value; but found [{}] instead"; TYPE; watchId; path;; token);
 value = XContentUtils.readValue(parser; token);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content