# An index has stayed on the same action longer than expected

**URL:** <https://discuss.elastic.co/t/an-index-has-stayed-on-the-same-action-longer-than-expected/339636>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [July 31, 2023, 3:31am UTC](https://discuss.elastic.co/t/an-index-has-stayed-on-the-same-action-longer-than-expected/339636 "2023-07-31T03:31:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nitinkapoor](https://avatars.discourse-cdn.com/v4/letter/n/5fc32e/32.png) [@nitinkapoor](https://discuss.elastic.co/u/nitinkapoor)\
**Post date:** [July 31, 2023, 3:31am UTC](https://discuss.elastic.co/t/an-index-has-stayed-on-the-same-action-longer-than-expected/339636/1 "2023-07-31T03:31:33Z")

</div>

I have upgraded my Elastic stack from 8.82 to 8.9 and facing this warning for one of my indices  
Deployment\_management  
Automatic index lifecycle and data retention management cannot make progress on one or more indices. The performance and stability of the indices and/or the cluster could be impacted.

How do I fix it , Kindly suggest

---

<div class="post-metadata">

**Author:** ![Keith\_Massey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keith_massey/32/83666_2.png) [@Keith\_Massey](https://discuss.elastic.co/u/Keith_Massey)\
**Post date:** [July 31, 2023, 9:53pm UTC](https://discuss.elastic.co/t/an-index-has-stayed-on-the-same-action-longer-than-expected/339636/2 "2023-07-31T21:53:37Z")

</div>

Hi @nitinkapoor. This is a new health check that we just added, and there is a decent chance that it might have discovered a problem that you have been having for some time. Can you post the full message? If you are only seeing that partial message through the Kibana UI, you can see the full thing using something like this in the kibana dev tools:  
`GET _health_report/ilm`  
You can see more options for this at [Health API | Elasticsearch Guide [8.9] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html). The response you get will give you some next steps for troubleshooting. It will probably ask you to use the [\_ilm/explain API](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-explain-lifecycle.html) for more information.

---

<div class="post-metadata">

**Author:** ![nitinkapoor](https://avatars.discourse-cdn.com/v4/letter/n/5fc32e/32.png) [@nitinkapoor](https://discuss.elastic.co/u/nitinkapoor)\
**Post date:** [August 1, 2023, 1:46am UTC](https://discuss.elastic.co/t/an-index-has-stayed-on-the-same-action-longer-than-expected/339636/3 "2023-08-01T01:46:06Z")

</div>

Thanks @Keith_Massey

I had dropped and recreated the index , the issue is resolved now but it was strange

If I change an existing ILM policy which is applied to couple of indices via respective index templates - if yes , how long it will take new policies to come into the action

Regards  
Nitin

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 29, 2023, 1:46am UTC](https://discuss.elastic.co/t/an-index-has-stayed-on-the-same-action-longer-than-expected/339636/4 "2023-08-29T01:46:52Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.