Could not parse watch status expecting field to be an object – 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 certain field to be an object, but it’s not. This could be due to incorrect data type or structure in the input. To resolve this issue, you should first check the data you’re trying to index and ensure that the field in question is correctly formatted as an object. If the data is correct, you may need to check your Elasticsearch mappings to ensure they align with the data you’re trying to index.

This guide will help you check for common problems that cause the log ” could not parse watch status. expecting field [{}] to be an object; ” 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 be an object;” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 ActionStatus actionStatus = ActionStatus.parse(currentFieldName; parser);
 actions.put(currentFieldName; actionStatus);
 } else {
 throw new ElasticsearchParseException("could not parse watch status. expecting field [{}] to be an object; " +
 "found [{}] instead"; currentFieldName; token);
 } else if (Field.HEADERS.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token == XContentParser.Token.START_OBJECT) {
 headers = parser.mapStrings();


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?