Invalid time minute value expected string number value but found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

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 an invalid minute value in a time field. It expects a string or number but found a different data type. This could be due to incorrect data input or a mismatch in the expected data type. To resolve this, ensure that the minute value is a string or number. Check your data input or mapping to ensure it matches the expected data type. If you’re using a script or application to input data, ensure it’s correctly formatted before sending to Elasticsearch.

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 ” invalid time minute value. expected string/number value; 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 “invalid time minute value. expected string/number value; but found [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } catch (NumberFormatException nfe) {
 throw new ElasticsearchParseException("invalid time minute value [{}]"; value);
 }  default:
 throw new ElasticsearchParseException("invalid time minute value. expected string/number value; but found [{}]"; token);
 }  }


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?