Could not parse trigger for expected END OBJECT token but found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is unable to parse a trigger due to an unexpected token in the JSON object. This usually happens when the JSON syntax is incorrect or malformed. To resolve this issue, you can: 1) Check the JSON syntax for any errors or missing brackets, 2) Validate the JSON object using a JSON validator, 3) Ensure that the JSON object is properly formatted according to the Elasticsearch documentation.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” could not parse trigger [{}] for [{}]. expected [END_OBJECT] token; but 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 trigger [{}] for [{}]. expected [END_OBJECT] token; but found [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 " but found [{}]"; type; jobName; token);
 Trigger trigger = parseTrigger(jobName; type; parser);
 token = parser.nextToken();
 if (token != XContentParser.Token.END_OBJECT) {
 throw new ElasticsearchParseException("could not parse trigger [{}] for [{}]. expected [END_OBJECT] token; but found [{}]";
 type; jobName; token);
 return trigger;


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?

Get expert answers on Elasticsearch/OpenSearch