# Uptime error
**URL:** https://discuss.elastic.co/t/uptime-error/234791
**Category:** Synthetics
**Created:** [May 28, 2020, 5:38pm UTC](https://discuss.elastic.co/t/uptime-error/234791 "2020-05-28T17:38:21Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@h\_e\_m](https://discuss.elastic.co/u/h_e_m)
#### Post date: [May 28, 2020, 5:38pm UTC](https://discuss.elastic.co/t/uptime-error/234791/1 "2020-05-28T17:38:21Z")
Hi!
I run elastic cloud with Kibana 7.6.1 since a few months, and my Uptime suddenly started to display
```auto
Error: [illegal_argument_exception] Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [monitor.id] in order to load field data by uninverting the inverted index. Note that this can use significant memory.
```
instead of the list of monitors. The graph show up fine thus.
It was working before and I have not changed the mapping created by Uptime when I set it up. The mapping for monitor.id is
```auto
"monitor": {
...
"id": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
},
```
Any clues on how to get Uptime working is appreciated.
Thanks
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [June 19, 2020, 12:39am UTC](https://discuss.elastic.co/t/uptime-error/234791/2 "2020-06-19T00:39:11Z")
Sorry to hear about this issue and apologies for the delay. It looks like an incorrect mapping has been applied. Typically this is caused by deleting the heartbeat indices while heartbeat is still running, causing default mappings to be applied by the next heartbeat write.
To fix this:
1. Stop all heartbeat instances
2. Delete all heartbeat indices
3. Start you heartbeat indices.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 13, 2020, 12:52am UTC](https://discuss.elastic.co/t/uptime-error/234791/3 "2020-07-13T00:52:37Z")
This topic was automatically closed 24 days after the last reply. New replies are no longer allowed.