Current step for index with policy is not recognized – How to solve related issues

Current step for index with policy is not recognized – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Current step for index with policy is not recognized ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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 :

     public void maybeRunAsyncAction(ClusterState currentState; IndexMetaData indexMetaData; String policy; StepKey expectedStepKey) {
        String index = indexMetaData.getIndex().getName();
        LifecycleExecutionState lifecycleState = LifecycleExecutionState.fromIndexMetadata(indexMetaData);
        Step currentStep = getCurrentStep(stepRegistry; policy; indexMetaData; lifecycleState);
        if (currentStep == null) {
            logger.warn("current step [{}] for index [{}] with policy [{}] is not recognized";
                getCurrentStepKey(lifecycleState); index; policy);

        logger.trace("[{}] maybe running async action step ({}) with current step {}";


Run the Check-Up to get customized recommendations like this:


The high disk watermark threshold is about to be reached in specific nodes



There are various “watermark” thresholds on each Elasticsearch cluster. When the high disk watermark threshold has been exceeded, it means disk space is running out. The node will…



Based on your specific ES deployment you should…


X-PUT curl -H [a customized code snippet to resolve the issue]

Optimize Elasticsearch Performance

Run The Tool