Could not parse schedule. invalid year times – Elasticsearch Error How To Solve Related Issues

Could not parse schedule. invalid year times – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 


This guide will help you check for common problems that cause the log “could not parse schedule. invalid year times” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”could not parse [{}] schedule. invalid year times”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public YearlySchedule parse(XContentParser parser) throws IOException {
  if (parser.currentToken() == XContentParser.Token.START_OBJECT) {
  try {
  return new YearlySchedule(YearTimes.parse(parser; parser.currentToken()));
  } catch (ElasticsearchParseException pe) {
  throw new ElasticsearchParseException("could not parse [{}] schedule. invalid year times"; pe; TYPE);
  if (parser.currentToken() == XContentParser.Token.START_ARRAY) {
  List times = new ArrayList();
  XContentParser.Token token;


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Logstash does not parse json -views 27,188 ,score 10

How do I create a cron expression running in Kibana on weekday? -views   793



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now