# Allow\_auto\_create set to false in all templates after uprgade to 8.12.0

**URL:** <https://discuss.elastic.co/t/allow-auto-create-set-to-false-in-all-templates-after-uprgade-to-8-12-0/359654>\
**Category:** Elasticsearch\
**Created:** [May 16, 2024, 3:55pm UTC](https://discuss.elastic.co/t/allow-auto-create-set-to-false-in-all-templates-after-uprgade-to-8-12-0/359654 "2024-05-16T15:55:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![logger](https://avatars.discourse-cdn.com/v4/letter/l/34f0e0/32.png) [@logger](https://discuss.elastic.co/u/logger)\
**Post date:** [May 16, 2024, 3:55pm UTC](https://discuss.elastic.co/t/allow-auto-create-set-to-false-in-all-templates-after-uprgade-to-8-12-0/359654/1 "2024-05-16T15:55:05Z")

</div>

Hi,

I have seen another "[Other thread with no answer](https://discuss.elastic.co/t/cannot-create-new-data-stream-from-auto-create/353958)" where the "allow\_auto\_create" is not working properly.

In my cluster the setting is true by default:

```auto
GET _cluster/settings
{
  "persistent": {
    "action": {
      "auto_create_index": "true"
    },
    "cluster": {
      "indices": {
        "close": {
          "enable": "true"
        }
      }, ... more settings

```

But all my templates now have now the "allow\_auto\_create" set to false.  
Is this a known "bug" or feature?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/0/f08e4039db5009ffadd6c882bd0a266e1b8bf162.png)

I also get the same error message like a component template forbids....

Will this override the settings again in the future? Or can I change it once?

Greetings  
logger

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [May 16, 2024, 4:29pm UTC](https://discuss.elastic.co/t/allow-auto-create-set-to-false-in-all-templates-after-uprgade-to-8-12-0/359654/2 "2024-05-16T16:29:32Z")

</div>

Yes, it is a bug, it was introduced in this PR: [Add allow auto create to index templates by Ikuni17 · Pull Request #170079 · elastic/kibana · GitHub](https://github.com/elastic/kibana/pull/170079)

It was fixed in this PR: [[Index Management] Fix allow\_auto\_create field in index template form by ElenaStoeva · Pull Request #178321 · elastic/kibana · GitHub](https://github.com/elastic/kibana/pull/178321)

The fix is on 8.13.3

I had the same issue that lead to data loss as new indices were not being created, the solution in my case was to edit hundreds of templates to set `allow_auto_create` to true.