# Disabling Rollover in ILM cause to error on retry lifecycle step

**URL:** <https://discuss.elastic.co/t/disabling-rollover-in-ilm-cause-to-error-on-retry-lifecycle-step/226619>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [April 6, 2020, 5:47am UTC](https://discuss.elastic.co/t/disabling-rollover-in-ilm-cause-to-error-on-retry-lifecycle-step/226619 "2020-04-06T05:47:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arman\_Ajdani](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arman_ajdani/32/47196_2.png) [@Arman\_Ajdani](https://discuss.elastic.co/u/Arman_Ajdani)\
**Post date:** [April 6, 2020, 5:47am UTC](https://discuss.elastic.co/t/disabling-rollover-in-ilm-cause-to-error-on-retry-lifecycle-step/226619/1 "2020-04-06T05:47:09Z")

</div>

Currently, I have an ILM Policy set to rollover and warm phase action, but of error :

```auto
illegal_argument_exception: index.lifecycle.rollover_alias [oauth] does not point to index [oauth-2020.02.24]

```

I decided to disable rollover , now when I try to retry lifecycle step I get this error :

```auto
[remote_transport_exception] [host][ip:port][indices:admin/ilm/retry]

```

What Can I do?

---

<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:** [May 4, 2020, 5:47am UTC](https://discuss.elastic.co/t/disabling-rollover-in-ilm-cause-to-error-on-retry-lifecycle-step/226619/2 "2020-05-04T05:47:13Z")

</div>

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