Could not parse watch status. expecting field to hold a string – How to solve this Elasticsearch error

Average Read Time

2 Mins

Could not parse watch status. expecting field to hold a string – 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 Check-Up which can resolve issues that cause many errors.

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

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

}
 } else if (Field.EXECUTION_STATE.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token.isValue()) {
 executionState = ExecutionState.resolve(parser.text());
 } else {
 throw new ElasticsearchParseException("could not parse watch status. expecting field [{}] to hold a string " +
 "value; found [{}] instead"; currentFieldName; token);
 }
 } else if (Field.ACTIONS.match(currentFieldName; parser.getDeprecationHandler())) {
 actions = new HashMap<>();
 if (token == XContentParser.Token.START_OBJECT) {

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content