Could not parse schedule invalid time value for field – – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch is unable to parse the schedule due to an invalid time value. This could be because the time value is not in the correct format or it’s outside the acceptable range. To resolve this issue, you should first check the format of the time value and ensure it matches the expected format. If the format is correct, then check if the time value is within the acceptable range. If neither of these solutions work, there might be an issue with the field itself, so check if it’s correctly defined.

This guide will help you check for common problems that cause the log ” could not parse [{}] schedule. invalid time value for field [{}] – [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “could not parse [{}] schedule. invalid time value for field [{}] – [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (AT_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token != XContentParser.Token.START_ARRAY) {
 try {
 times.add(DayTimes.parse(parser; token));
 } catch (ElasticsearchParseException pe) {
 throw new ElasticsearchParseException("could not parse [{}] schedule. invalid time value for field [{}] - [{}]";
 pe; TYPE; currentFieldName; token);
 } else {
 while ((token = parser.nextToken()) != XContentParser.Token.END_ARRAY) {
 try {


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?