Expected at but found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch encounters a mismatch between the expected data type or format and the actual data provided. This could be due to incorrect data types, incorrect JSON format, or missing required fields. To resolve this issue, you should first verify the data type and format of the input data. Ensure that it matches the expected format or data type. If the error persists, check if all required fields are provided in the request. Lastly, validate your JSON input to ensure it’s correctly formatted.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” : expected [{}] (at [{}]) but found [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “: expected [{}] (at [{}]) but found [{}]” class name is Intervals.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // char token
 if (token.ch != 0) {
 char found = string.charAt(startToken);
 if (found != token.ch) {
 throw new ParsingException(source; invalidIntervalMessage(string) + ": expected [{}] (at [{}]) but found [{}]";
 token.ch; startToken; found);
 // number char


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?