Failed step for index is not part of policy anymore or it is invalid – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-7.15

Briefly, this error occurs when an index lifecycle management (ILM) policy step fails because the step is either no longer part of the policy or it is invalid. To resolve this issue, you can either update the ILM policy to include the missing step or correct the invalid step. Alternatively, you can manually move the index to the next step using the Move to step API. Lastly, you can also delete and recreate the index with a valid ILM policy.

This guide will help you check for common problems that cause the log ” failed step [{}] for index [{}] is not part of policy [{}] anymore; or it is invalid ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, plugin.

Log Context

Log “failed step [{}] for index [{}] is not part of policy [{}] anymore; or it is invalid” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            // if the error is transient/recoverable from
            // maintain the retry count of the failed step as it will be cleared after a successful execution
        } else {
            logger.warn("failed step [{}] for index [{}] is not part of policy [{}] anymore; or it is invalid";
                currentStep.getName(); index; policyMetadata.getName());

        ClusterState.Builder newClusterStateBuilder = newClusterStateWithLifecycleState(index; clusterState;;


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?