Failed to parse action expected to be of type string but – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch tries to parse a field that it expects to be a string, but it’s not. This could be due to incorrect data types in the index mapping or incorrect data input. To resolve this, you can check and correct the data type in your index mapping or ensure the input data matches the expected data type. If the error persists, you may need to reindex your data with the correct mapping.

This guide will help you check for common problems that cause the log ” failed to parse [{}] action [{}/{}]. expected [{}] to be of type string; but ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “failed to parse [{}] action [{}/{}]. expected [{}] to be of type string; but” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 currentFieldName = parser.currentName();
 } else if (Field.ACCOUNT.match(currentFieldName; parser.getDeprecationHandler())) {
 if (token == XContentParser.Token.VALUE_STRING) {
 account = parser.text();
 } else {
 throw new ElasticsearchParseException("failed to parse [{}] action [{}/{}]. expected [{}] to be of type string; but " +
 "found [{}] instead"; TYPE; watchId; actionId; Field.ACCOUNT.getPreferredName(); token);
 } else if (Field.PROXY.match(currentFieldName; parser.getDeprecationHandler())) {
 proxy = HttpProxy.parse(parser);
 } else if (Field.FIELDS.match(currentFieldName; parser.getDeprecationHandler())) {


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?