Could not parse action unexpected number field – 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 due to an unexpected number field. This could be due to incorrect data types, a malformed request, or a syntax error in the query. To resolve this issue, you should first verify the data types in your request. Ensure that the number field is correctly formatted and matches the expected data type. If the error persists, check the syntax of your query for any errors or inconsistencies. Lastly, ensure that your request is correctly structured and adheres to the Elasticsearch API guidelines.

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

 } else if (token == XContentParser.Token.VALUE_NUMBER) {
 if (Field.TIMEOUT.match(currentFieldName; parser.getDeprecationHandler())) {
 timeout = timeValueMillis(parser.longValue());
 } else {
 throw new ElasticsearchParseException("could not parse [{}] action [{}/{}]. unexpected number field [{}]"; TYPE;
 watchId; actionId; currentFieldName);
 } else if (token == XContentParser.Token.VALUE_STRING) {
 if (Field.DOC_TYPE.match(currentFieldName; parser.getDeprecationHandler())) {
 deprecationLogger.deprecate(DeprecationCategory.TYPES; "watcher_index_action"; TYPES_DEPRECATION_MESSAGE);


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?