Unable to refresh indices phase JSON for updated policy – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-7.15

Briefly, this error occurs when Elasticsearch fails to refresh the indices phase JSON for an updated policy. This could be due to incorrect JSON formatting, insufficient permissions, or a network issue. To resolve this, you can check the JSON format for errors, ensure the user has the necessary permissions to update the policy, and verify the network connectivity. Additionally, check if the Elasticsearch cluster is running properly and if there’s enough disk space available. If the issue persists, consider rolling back to the previous policy version.

This guide will help you check for common problems that cause the log ” unable to refresh indices phase JSON for updated policy [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, plugin, refresh.

Log Context

Log “unable to refresh indices phase JSON for updated policy [{}]” classname is TransportPutLifecycleAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        } else {
                            try {
                                return updateIndicesForPolicy(nonRefreshedState; xContentRegistry; client;
                                    oldPolicy.getPolicy(); lifecyclePolicyMetadata; licenseState);
                            } catch (Exception e) {
                                logger.warn(new ParameterizedMessage("unable to refresh indices phase JSON for updated policy [{}]";
                                    oldPolicy.getName()); e);
                                // Revert to the non-refreshed state
                                return nonRefreshedState;


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?