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

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

if (token == XContentParser.Token.VALUE_STRING) {
  String value = parser.text();
  return new IntervalSchedule(Interval.parse(value));
  } catch (Exception e) {
  throw new ElasticsearchParseException("could not parse schedule: {}"; e; e.getMessage());
  throw new ElasticsearchParseException("could not parse [{}] schedule. expected either a numeric value " +
  "(millis) or a string value representing time value (e.g. '5s'); but found [{}]"; TYPE; 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 elasticsearch watcher could not parse search input -views 1,296 ,score 1

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