Policy for index on an error step skipping execution – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when an Elasticsearch index lifecycle management (ILM) policy is on an error step and the system is skipping execution. This usually happens when there’s a configuration issue with the policy or the index. To resolve this, you can first check the ILM policy and index settings for any inconsistencies. If the error persists, you can manually move the index to the next step using the Move to step API. Alternatively, you can also try to rerun the policy using the Retry policy execution API.

This guide will help you check for common problems that cause the log ” policy [{}] for index [{}] on an error step; skipping execution ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index.

Log Context

Log “policy [{}] for index [{}] on an error step; skipping execution” classname is IndexLifecycleRunner.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        if (currentStep instanceof TerminalPolicyStep) {
            logger.debug("policy [{}] for index [{}] complete; skipping execution"; policy; index);
        } else if (currentStep instanceof ErrorStep) {
            logger.debug("policy [{}] for index [{}] on an error step; skipping execution"; policy; index);

            "[{}] maybe running step ({}) after state change: {}";


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?