Briefly, this error occurs when Elasticsearch is unable to interpret the cron schedule due to incorrect format. The cron schedule should be either a string value or an array. To resolve this, ensure that the cron expression is correctly formatted. If it’s a string, it should be enclosed in quotes. If it’s an array, it should be enclosed in square brackets. Also, verify that the cron expression is valid and adheres to the cron syntax rules.
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. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “could not parse [cron] schedule. expected either a cron string value or an array” class name 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 + "]");
}
}
}
}
