# Error on lifecycle policy alias

**URL:** <https://discuss.elastic.co/t/error-on-lifecycle-policy-alias/340337>\
**Category:** Elasticsearch\
**Created:** [August 8, 2023, 8:09am UTC](https://discuss.elastic.co/t/error-on-lifecycle-policy-alias/340337 "2023-08-08T08:09:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fribse](https://avatars.discourse-cdn.com/v4/letter/f/c67d28/32.png) [@fribse](https://discuss.elastic.co/u/fribse)\
**Post date:** [August 8, 2023, 8:09am UTC](https://discuss.elastic.co/t/error-on-lifecycle-policy-alias/340337/1 "2023-08-08T08:09:00Z")

</div>

I wasn't aware of the alias requirement on lifecycle management, so now I have a ton of data imported, on indexes with this pattern based on an index template:  
dmarc-7.17.4-2023.08  
Where the version, year and month varies of course.

I have other indexes with the same challenge.

Is there a way I can fix it for them, so I get lifetime management to work properly?

---

<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:** [September 5, 2023, 8:09am UTC](https://discuss.elastic.co/t/error-on-lifecycle-policy-alias/340337/2 "2023-09-05T08:09:52Z")

</div>

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