Could not parse watch watch status in invalid state action – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch cannot parse a watch due to an invalid state. This could be due to incorrect syntax, missing required fields, or invalid data in the watch definition. To resolve this issue, you can: 1) Check the watch definition for any syntax errors or missing required fields. 2) Validate the data being used in the watch. 3) If the watch was recently updated, try reverting to a previous version to see if the error persists. 4) Restart Elasticsearch to clear any temporary issues.

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

 if (status != null) {
 // verify the status is valid (that every action indeed has a status)
 for (ActionWrapper action : actions) {
 if (status.actionStatus(action.id()) == null) {
 throw new ElasticsearchParseException("could not parse watch [{}]. watch status in invalid state. action [{}] " +
 "status is missing"; id; action.id());
 }
 }
 } else {
 // we need to create the initial statuses for the actions

 

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?