# Curator 7.0.1 fails because of closed indices **URL:** \ **Category:** Elasticsearch\ **Tags:** curator\ **Created:** [January 14, 2025, 4:29pm UTC](https://discuss.elastic.co/t/curator-7-0-1-fails-because-of-closed-indices/373190 "2025-01-14T16:29:33Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [February 5, 2025, 11:02pm UTC](https://discuss.elastic.co/t/curator-7-0-1-fails-because-of-closed-indices/373190/4 "2025-02-05T23:02:27Z")
I think you'll find this reply I recently made could help address this: > [@Issues when running curator 8.0.17](https://discuss.elastic.co/t/issues-when-running-curator-8-0-17/372996/15): > > I really do not know why the value: "^\\.\*" pattern isn't working for you: actions: 1: description: "This action should not affect anything. It's here to show filter behavior" action: open options: allow\_ilm\_indices: True filters: - filtertype: pattern kind: regex exclude: true value: "^\\.\*" Sample of debug log output from my own cluster running 8.17.0: 2025-02-05 11:04:42,769 DEBUG curator.indexlist iterate\_filters:1452 I… The snippet doesn't get to the good part, which is the `index_pattern` option. --- _[View the full topic](https://discuss.elastic.co/t/curator-7-0-1-fails-because-of-closed-indices/373190)._