Current step for index with policy is not recognized – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch cannot recognize the current step of an index lifecycle management (ILM) policy. This could be due to a misconfiguration or an unsupported step in the policy. To resolve this issue, you can check the ILM policy configuration for any errors or unsupported steps. If the policy is correct, try to manually move the index to the next step using the Move to step API. If the error persists, you may need to delete and recreate the ILM policy.

This guide will help you check for common problems that cause the log ” current step [{}] for index [{}] with policy [{}] is not recognized ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index.

Log Context

Log “current step [{}] for index [{}] with policy [{}] is not recognized” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    // This index is a leftover from before we halted execution on the final phase
                    // instead of going to the completed phase; so it's okay to ignore this index
                    // for now
                logger.error("current step [{}] for index [{}] with policy [{}] is not recognized"; currentStepKey; index; policy);

        if (currentStep instanceof TerminalPolicyStep) {


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?