Could not parse action for watch failed to parse must be – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch is unable to parse a specific action for a watch. This could be due to incorrect syntax, missing fields, or invalid data types in the watch definition. To resolve this issue, you should first verify the syntax of your watch definition. Make sure all required fields are included and that the data types are correct. If the error persists, try to isolate the problematic part by simplifying your watch definition, then gradually add complexity until the error reappears. This will help you identify the exact cause of the problem.

This guide will help you check for common problems that cause the log ” could not parse [{}] action for watch [{}]. failed to parse [{}]. must be ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index.

Log Context

Log “could not parse [{}] action for watch [{}]. failed to parse [{}]. must be” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 timeout = WatcherDateTimeUtils.parseTimeValue(parser; Field.TIMEOUT_HUMAN.toString());
 } else if (Field.DYNAMIC_NAME_TIMEZONE.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token == XContentParser.Token.VALUE_STRING) {
 dynamicNameTimeZone = DateUtils.of(parser.text());
 } else {
 throw new ElasticsearchParseException("could not parse [{}] action for watch [{}]. failed to parse [{}]. must be " +
 "a string value (e.g. 'UTC' or '+01:00')."; TYPE; watchId; currentFieldName);
 } else if (Field.REFRESH.match(currentFieldName; parser.getDeprecationHandler())) {
 refreshPolicy = RefreshPolicy.parse(parser.text());
 } else {


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?