Could not parse schedule unexpected token – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to parse a schedule due to an unexpected token. This usually happens when there’s a syntax error in the cron expression or the schedule format is incorrect. To resolve this issue, you should first verify the cron expression or schedule format. Ensure it follows the correct syntax and doesn’t contain any unexpected characters. If the problem persists, check for any updates or patches that might fix this issue. Lastly, consider seeking help from the Elasticsearch community or support if you can’t resolve the issue yourself.

This guide will help you check for common problems that cause the log ” could not parse [{}] schedule. unexpected token [{}] ” 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 [{}] schedule. unexpected token [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 XContentParser.Token token;
 while ((token = parser.nextToken()) != XContentParser.Token.END_OBJECT) {
 if (token == XContentParser.Token.FIELD_NAME) {
 currentFieldName = parser.currentName();
 } else if (currentFieldName == null) {
 throw new ElasticsearchParseException("could not parse [{}] schedule. unexpected token [{}]"; TYPE; token);
 } else if (MINUTE_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token.isValue()) {
 try {
 minutes.add(DayTimes.parseMinuteValue(parser; token));
 } catch (ElasticsearchParseException pe) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?