Could not parse condition for watch – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch is unable to parse the condition specified for a watch. This could be due to incorrect syntax, missing or invalid parameters. To resolve this issue, you should first verify the syntax of your condition. Ensure that all required parameters are included and correctly formatted. If the error persists, check the Elasticsearch logs for more detailed information about the parsing error. You may also need to update or reinstall the watch plugin if it’s outdated or corrupted.

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 [{}].” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (token == XContentParser.Token.FIELD_NAME) {
 if (parser.currentName().equals("value")) {
 token = parser.nextToken();
 if (op.supportsStructures() == false && token.isValue() == false
 && 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);


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?