Could not parse schedule invalid weekly times – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch cannot interpret the schedule provided due to incorrect formatting or invalid values. The schedule is likely set for a weekly task, but the time values are not recognized. To resolve this, ensure that the schedule is formatted correctly according to Elasticsearch’s cron expressions. Check for any typos or incorrect values. Also, ensure that the time values are within the valid range. If the problem persists, consider resetting the schedule to a default value and then reconfiguring it.

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

 public WeeklySchedule parse(XContentParser parser) throws IOException {
 if (parser.currentToken() == XContentParser.Token.START_OBJECT) {
 try {
 return new WeeklySchedule(WeekTimes.parse(parser; parser.currentToken()));
 } catch (ElasticsearchParseException pe) {
 throw new ElasticsearchParseException("could not parse [{}] schedule. invalid weekly times"; pe; TYPE);
 if (parser.currentToken() == XContentParser.Token.START_ARRAY) {
 List times = new ArrayList<>();
 XContentParser.Token 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?