Skipping policy execution of step for index with policy – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.4-7.15

Briefly, this error occurs when Elasticsearch’s Index Lifecycle Management (ILM) tries to execute a policy on an index, but skips it due to certain conditions not being met. This could be due to the index being in an unexpected state or the policy’s conditions not being satisfied. To resolve this, you can review the ILM policy and its conditions, check the index state, and ensure that the index meets the policy’s requirements. If necessary, you can also manually move the index to the next step using the Move to step API.

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

Log Context

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

                                    idxMeta.getIndex().getName(); policyName; stepKey.getName());
                                lifecycleRunner.maybeRunAsyncAction(clusterState; idxMeta; policyName; stepKey);
                                // ILM is trying to stop; but this index is in a Shrink step (or other dangerous step) so we can't stop
                                safeToStop = false;
                            } else {
                      "skipping policy execution of step [{}] for index [{}] with policy [{}]" +
                                        " because ILM is stopping";
                                    stepKey == null ? "n/a" : stepKey.getName(); idxMeta.getIndex().getName(); policyName);
                        } else {
                            lifecycleRunner.maybeRunAsyncAction(clusterState; idxMeta; policyName; stepKey);