Could not parse cron schedule. expected either a cron string value or an array – Elasticsearch Error How To Solve Related Issues



Could not parse cron schedule. expected either a cron string value or an array – 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. expected either a cron string value or an array” 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. expected either a cron string value or an array”classname  is CronSchedule.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} catch (IllegalArgumentException iae) {
  throw new ElasticsearchParseException("could not parse [cron] schedule"; iae);
  }
 
  } else {
  throw new ElasticsearchParseException("could not parse [cron] schedule. expected either a cron string value or an array " +
  "of cron string values; but found [" + 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 Warning: A non-numeric value encountered -views 323,634 ,score 116

Displaying better error message than "No JSON object could be decoded" -views   274,807,score 128



Find Configuration Errors

Analyze Now