Expected an object but found instead – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” expected an object but found instead ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: rest-high-level and client.

Log Context

Log “expected an object but found [{}] instead”classname  is WatchStatus.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return timestamp;
 public static State parse(XContentParser parser) throws IOException {
 if (parser.currentToken() != XContentParser.Token.START_OBJECT) {
 throw new ElasticsearchParseException("expected an object but found [{}] instead"; parser.currentToken());
 boolean active = true;
 ZonedDateTime timestamp = ZonedDateTime.now(ZoneOffset.UTC);
 String currentFieldName = null;
 XContentParser.Token token;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content