# Fields disappear after refreshing on visualization pages

**URL:** <https://discuss.elastic.co/t/fields-disappear-after-refreshing-on-visualization-pages/86171>\
**Category:** Kibana\
**Created:** [May 17, 2017, 8:52pm UTC](https://discuss.elastic.co/t/fields-disappear-after-refreshing-on-visualization-pages/86171 "2017-05-17T20:52:41Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\
**Post date:** [May 24, 2017, 8:11pm UTC](https://discuss.elastic.co/t/fields-disappear-after-refreshing-on-visualization-pages/86171/14 "2017-05-24T20:11:57Z")

</div>

It looks like you're hitting Kibana and/or Elasticsearch's max payload size. These are configurable via Kibana's [maxPayloadBytes](https://www.elastic.co/guide/en/kibana/4.5/kibana-server-properties.html) and Elasticsearch's [http.max\_content\_length](https://www.elastic.co/guide/en/elasticsearch/reference/2.3/modules-http.html).

But it sounds like you're saying this large number of fields is unexpected? I notice your index pattern is just `*`. Are you casting too wide of a net and including indices that you don't intend to perhaps? If you look at the response to the GET request for `<kibana-url>/elasticsearch/*/_mapping/field/*` (before the one that fails) you can see all of the fields from all of the indices that are getting pulled back.

---

_[View the full topic](https://discuss.elastic.co/t/fields-disappear-after-refreshing-on-visualization-pages/86171)._