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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

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: index and plugin.

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 {}";


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content