Invalid gap policy text accepted values – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

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 an incorrect gap policy is specified in an Elasticsearch aggregation query. The gap policy determines how to handle gaps in data. Accepted values are typically “skip” or “insert_zeros”. To resolve this issue, check your query and ensure that the gap policy is correctly specified. If it’s not, replace it with an accepted value. If you’re unsure, use “skip” to ignore gaps or “insert_zeros” to fill them with zeros.

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 ” Invalid gap policy: [” + text + “]; accepted values: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search, aggregations.

Log Context

Log “Invalid gap policy: [” + text + “]; accepted values: ” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (result == null) {
 final List validNames = new ArrayList<>();
 for (GapPolicy policy : values()) {
 throw new ParsingException(tokenLocation; "Invalid gap policy: [" + text + "]; accepted values: " + validNames);
 return result;
 }  private final byte id;


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