Could not parse watch status expecting field to hold a long – 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 watch status because it expects a field to hold a long (a type of data) but it’s receiving a different data type. To resolve this issue, you can check the data type of the field in question and ensure it’s a long. If it’s not, you need to convert it to a long. Also, ensure that the field is not null or empty as this could also cause the error. Lastly, check your Elasticsearch version, as older versions may have bugs that cause this error.

This guide will help you check for common problems that cause the log ” could not parse watch status. expecting field [{}] to hold a long ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: rest-high-level, client.

Log Context

Log “could not parse watch status. expecting field [{}] to hold a long” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (Field.VERSION.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token.isValue()) {
 version = parser.longValue();
 } else {
 throw new ElasticsearchParseException("could not parse watch status. expecting field [{}] to hold a long " +
 "value; found [{}] instead"; currentFieldName; token);
 } else if (Field.LAST_CHECKED.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token.isValue()) {
 lastChecked = parseDate(currentFieldName; parser);