# No workflows running after lost elasticsearch index

**URL:** <https://community.temporal.io/t/no-workflows-running-after-lost-elasticsearch-index/4518>\
**Category:** Community Support\
**Tags:** elasticsearch, advanced\_visibility\
**Created:** [April 22, 2022, 9:46am UTC](https://community.temporal.io/t/no-workflows-running-after-lost-elasticsearch-index/4518 "2022-04-22T09:46:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![o.kolobov](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/o.kolobov/32/1980_2.png) [@o.kolobov](https://community.temporal.io/u/o.kolobov)\
**Post date:** [April 22, 2022, 9:46am UTC](https://community.temporal.io/t/no-workflows-running-after-lost-elasticsearch-index/4518/1 "2022-04-22T09:46:42Z")

</div>

Hello.  
Temporal with Cassandra installed via helm with Elastic.  
We lost the elastic index (elasticsearch.persistance was disabled in helm values by inattention), after that we recreated the index: list of workflows is lost.  
Also, previously scheduled workflows were not running after the index was lost.  
I have 2 questions:

1. Should workflows run when Elastic is unavailable? I thought that unavailability of Elastic should not affect the launch of already scheduled processes: [What happens if ES for visibility is down?](https://community.temporal.io/t/what-happens-if-es-for-visibility-is-down/2064)
2. Is it possible to restore the list of worker processes to Elastic index from Cassandra?  
Thanks.

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [April 22, 2022, 6:12pm UTC](https://community.temporal.io/t/no-workflows-running-after-lost-elasticsearch-index/4518/2 "2022-04-22T18:12:33Z")

</div>

1. Yes, workflows should keep running even if ES is down.
2. This is not currently supported.