Could not parse watch status expecting field to hold a string – 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 specific field to contain a string, but it doesn’t. This could be due to incorrect data type or malformed JSON. To resolve this, ensure that the field in question contains a string as expected. Check your JSON formatting for any errors. Also, verify your data types and ensure they match what Elasticsearch expects. If you’re using a script or application to generate this data, check it for bugs or incorrect data handling.

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, client.

Log Context

Log “could not parse watch status. expecting field [{}] to hold a string” class name is 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) {


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?