# Cannot create new data stream from auto-create

**URL:** <https://discuss.elastic.co/t/cannot-create-new-data-stream-from-auto-create/353958>\
**Category:** Elasticsearch\
**Created:** [February 23, 2024, 8:59am UTC](https://discuss.elastic.co/t/cannot-create-new-data-stream-from-auto-create/353958 "2024-02-23T08:59:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hti](https://avatars.discourse-cdn.com/v4/letter/h/e19b73/32.png) [@hti](https://discuss.elastic.co/u/hti)\
**Post date:** [February 23, 2024, 8:59am UTC](https://discuss.elastic.co/t/cannot-create-new-data-stream-from-auto-create/353958/1 "2024-02-23T08:59:28Z")

</div>

Hello,

since the last update from 8.10.3 to 8.12.1 we have issues creating new data streams.  
We do see error messages such as "no such index [composable template [logs-cape.\*] forbids index auto creation]"

The cluster setting actions.auto\_create\_index defaults to true and setting it to true explicitly does not help. A possible workaround is to explicitly set "allow auto create" to true in the index template.

Has this behaviour changed in a recent version?  
The documentation still states, that "allow auto create" should not affect data streams at all and it should default to true.

Best regards,  
Timo

---

<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:** [March 22, 2024, 8:59am UTC](https://discuss.elastic.co/t/cannot-create-new-data-stream-from-auto-create/353958/2 "2024-03-22T08:59:41Z")

</div>

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