# GraphQL errors uptime heartbeat
**URL:** https://discuss.elastic.co/t/graphql-errors-uptime-heartbeat/178473
**Category:** Synthetics
**Created:** [April 25, 2019, 1:30pm UTC](https://discuss.elastic.co/t/graphql-errors-uptime-heartbeat/178473 "2019-04-25T13:30:08Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@amergan](https://discuss.elastic.co/u/amergan)
#### Post date: [April 25, 2019, 1:30pm UTC](https://discuss.elastic.co/t/graphql-errors-uptime-heartbeat/178473/1 "2019-04-25T13:30:08Z")
After configuring heartbeat, i get these errors in uptime.
Error GraphQL error: [search\_context\_exception] unknown type for collapse field `monitor.id`, only keywords and numbers are acceptedError GraphQL error: [illegal\_argument\_exception] Fielddata is disabled on text fields by default. Set fielddata=true on [monitor.id] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.
Error GraphQL error: [illegal\_argument\_exception] Fielddata is disabled on text fields by default. Set fielddata=true on [monitor.id] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.
Error GraphQL error: [illegal\_argument\_exception] Fielddata is disabled on text fields by default. Set fielddata=true on [monitor.id] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [April 25, 2019, 9:31pm UTC](https://discuss.elastic.co/t/graphql-errors-uptime-heartbeat/178473/2 "2019-04-25T21:31:04Z")
This appears to be a race affecting all beats. We're looking into the issue here: [https://github.com/elastic/beats/issues/11940](https://github.com/elastic/beats/issues/11940)
---
### Author:  [@strawgate](https://discuss.elastic.co/u/strawgate)
#### Post date: [April 26, 2019, 4:21am UTC](https://discuss.elastic.co/t/graphql-errors-uptime-heartbeat/178473/3 "2019-04-26T04:21:44Z")
Make sure the index templates for 7.0.0 are imported and that you remove the existing indices which don't use the template.
---
### Author:  [@DavyVanKeymeulen](https://discuss.elastic.co/u/DavyVanKeymeulen)
#### Post date: [April 29, 2019, 2:39pm UTC](https://discuss.elastic.co/t/graphql-errors-uptime-heartbeat/178473/4 "2019-04-29T14:39:49Z")
Is there any fix to it?
Because I'm having the same problem.
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [April 29, 2019, 3:27pm UTC](https://discuss.elastic.co/t/graphql-errors-uptime-heartbeat/178473/5 "2019-04-29T15:27:34Z")
Yes, we're looking into it. Apologies for the issue.
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [April 30, 2019, 5:10pm UTC](https://discuss.elastic.co/t/graphql-errors-uptime-heartbeat/178473/6 "2019-04-30T17:10:23Z")
I've updated the Github issue here [https://github.com/elastic/beats/issues/11940](https://github.com/elastic/beats/issues/11940) with the root cause and a workaround. Please track the issue for further updates.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 24, 2019, 5:10pm UTC](https://discuss.elastic.co/t/graphql-errors-uptime-heartbeat/178473/7 "2019-05-24T17:10:23Z")
This topic was automatically closed 24 days after the last reply. New replies are no longer allowed.