# Error in visualisation; \[esaggs\] \> when trying to load a dashboard **URL:** \ **Category:** Kibana\ **Created:** [December 18, 2020, 10:52am UTC](https://discuss.elastic.co/t/error-in-visualisation-esaggs-when-trying-to-load-a-dashboard/259081 "2020-12-18T10:52:39Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![lukeelmers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukeelmers/32/35230_2.png) [@lukeelmers](https://discuss.elastic.co/u/lukeelmers)\ **Post date:** [December 18, 2020, 3:51pm UTC](https://discuss.elastic.co/t/error-in-visualisation-esaggs-when-trying-to-load-a-dashboard/259081/2 "2020-12-18T15:51:16Z")
> When opening one of these errors, no further information is given. Yeah, unfortunately these errors are not always the most helpful. What does the response from the server say if you use your browser dev tools to inspect network activity? Do you see any errors in the browser console? And what version of the stack are you running? Also worth noting that there is a max buckets setting that gets applied in Elasticsearch, as described in this thread: > [@Increasing max\_buckets for specific Visualizations](https://discuss.elastic.co/t/increasing-max-buckets-for-specific-visualizations/187390/4): > > Elasticsearch sets a default limit of 10000 for the search.max\_buckets setting. This can be changed, but it can also have a detrimental effect on the cluster, as you say if someone sends "killer queries". Kibana has a default limit of 2000 for the max buckets in the Advanced Settings under Management. This is a conservative limit and can be set higher. But passing a lot of data around in the browser can be extremely resource intensive and cause browser hangups. Perhaps we should try to optimiz… It doesn't _sound_ like you're running into this based on your description, but thought I'd mention it just in case. --- _[View the full topic](https://discuss.elastic.co/t/error-in-visualisation-esaggs-when-trying-to-load-a-dashboard/259081)._