# Uptime Just Spins

**URL:** https://discuss.elastic.co/t/uptime-just-spins/193900
**Category:** Synthetics
**Created:** [August 6, 2019, 12:24am UTC](https://discuss.elastic.co/t/uptime-just-spins/193900 "2019-08-06T00:24:53Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![richard\_N](https://avatars.discourse-cdn.com/v4/letter/r/ecb155/32.png) [@richard\_N](https://discuss.elastic.co/u/richard_N)
#### Post date: [August 6, 2019, 12:24am UTC](https://discuss.elastic.co/t/uptime-just-spins/193900/1 "2019-08-06T00:24:53Z")

</div>

Just setup a fresh 7.3 cluster across the board. Everything was working but I deleted an old heartbeat index and now my Uptime dashboard just spins. The index recreated correctly and I can view all heartbeats on the Discover dashboard but nothing on Uptime. I just get the loading screen and it never stops. Everything is set to defaults. Index pattern is default 7.3 index pattern. Template is there.

---

<div class="post-metadata">

### Author: ![richard\_N](https://avatars.discourse-cdn.com/v4/letter/r/ecb155/32.png) [@richard\_N](https://discuss.elastic.co/u/richard_N)
#### Post date: [August 6, 2019, 11:43am UTC](https://discuss.elastic.co/t/uptime-just-spins/193900/2 "2019-08-06T11:43:03Z")

</div>

I got it to work. I reindexed heartbeat to a temporary index, deleted all heartbeat-\* indices and templates, stopped heartbeat and ran setup again to reimport template and recreate index. I then reindexed my data back from temporary and everything works again.

---

<div class="post-metadata">

### Author: ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [August 10, 2019, 2:34am UTC](https://discuss.elastic.co/t/uptime-just-spins/193900/3 "2019-08-10T02:34:11Z")

</div>

Apologies for the delay here. This is something we're working to address but will need changes for ES core.

The central issue here is that if a beat has its indices deleted while running it will write directly to an alias and auto-create an index with the wrong mapping.

I've opened [https://github.com/elastic/kibana/issues/43071](https://github.com/elastic/kibana/issues/43071) to track the creation of a better error message.

---

<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 3, 2019, 2:34am UTC](https://discuss.elastic.co/t/uptime-just-spins/193900/4 "2019-09-03T02:34:12Z")

</div>

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