Invalid time minute value – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch receives an invalid minute value in a time field. This could be due to incorrect formatting or an out-of-range value. To resolve this issue, ensure that the minute value is between 0 and 59 and follows the correct time format. If you’re using a script or application to input data, check that it’s correctly generating and formatting time values. Also, validate your data before indexing to prevent such errors.

This guide will help you check for common problems that cause the log ” invalid time minute value [{}] ” 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 [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 yield minute;
 } 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 [{}]";


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?