Start object expected indices – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.9

Briefly, this error occurs when Elasticsearch expects a start object but doesn’t find one. This usually happens when there’s a syntax error in the JSON body of a request, specifically related to the “indices” field. To resolve this, you should check the JSON syntax of your request. Make sure that the “indices” field is correctly formatted and that all objects are properly opened and closed. Also, ensure that the “indices” field is not empty and contains valid data.

This guide will help you check for common problems that cause the log ” start object expected [indices] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories.

Log Context

Log “start object expected [indices]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else {
 throw new ElasticsearchParseException("expected array for [" + field + "]");
 } else if (INDICES.equals(field)) {
 if (parser.nextToken() != XContentParser.Token.START_OBJECT) {
 throw new ElasticsearchParseException("start object expected [indices]");
 while (parser.nextToken() != XContentParser.Token.END_OBJECT) {
 final String indexName = parser.currentName();
 final List snapshotIds = new ArrayList<>();
 final List gens = new ArrayList<>();


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?