Briefly, this error occurs when Elasticsearch is unable to parse a schedule due to missing or incorrect fields. This is often seen in Watcher, a plugin used for alerting and notification based on Elasticsearch data. The error suggests that the schedule type field is missing in the cron expression or interval schedule. To resolve this issue, ensure that the schedule field is correctly defined in the Watcher configuration. Check the syntax and structure of your cron expression or interval schedule. Make sure all required fields are present and correctly formatted.
This guide will help you check for common problems that cause the log ” could not parse schedule. expected a schedule type field; but no fields were found ” 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. expected a schedule type field; but no fields were found” class name is ScheduleRegistry.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
token
);
}
}
if (schedule == null) {
throw new ElasticsearchParseException("could not parse schedule. expected a schedule type field; but no fields were found");
}
return schedule;
} public Schedule parse(String context; String type; XContentParser parser) throws IOException {
