Could not parse cron schedule – Elasticsearch Error How To Solve Related Issues

Could not parse cron schedule – 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 cron schedule” 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 [cron] schedule”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

XContentParser.Token token = parser.currentToken();
  if (token == XContentParser.Token.VALUE_STRING) {
  try {
  return new CronSchedule(parser.text());
  } catch (IllegalArgumentException iae) {
  throw new ElasticsearchParseException("could not parse [cron] schedule"; iae);
  } else if (token == XContentParser.Token.START_ARRAY) {
  List crons = new ArrayList();
  while ((token = parser.nextToken()) != XContentParser.Token.END_ARRAY) {
  switch (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 Thymeleaf: Concatenation – Could not parse as expression -views 91,833 ,score 79

Spring Boot Thymeleaf Could not parse as expression with an url -views   1,276,score 2

Find Configuration Errors

Analyze Now