# The data you are seeing might be incomplete or wrong **URL:** \ **Category:** Elasticsearch\ **Created:** [December 10, 2019, 10:38pm UTC](https://discuss.elastic.co/t/the-data-you-are-seeing-might-be-incomplete-or-wrong/211386 "2019-12-10T22:38:49Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![t3fsx](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@t3fsx](https://discuss.elastic.co/u/t3fsx)\ **Post date:** [December 10, 2019, 10:38pm UTC](https://discuss.elastic.co/t/the-data-you-are-seeing-might-be-incomplete-or-wrong/211386/1 "2019-12-10T22:38:50Z")
Hi, Recently delete an index with `DELETE filebeat-7.5.0-2019.12.03-000001` and now I'm having all sorts of different issues with searching and visualizations. ``` The data you are seeing might be incomplete or wrong. ``` Is a message I see when trying to search. On visualizations I get: ``` 1 of 18 shards failed The data you are seeing might be incomplete or wrong. ``` as well as ``` [esaggs] > "field" is a required parameter ``` Any tips on how to fix this? I assume my command deleted the actual content of the index, not the index itself. Seeing as I have similar data, I don't understand what was dependent on that specific index. I also now have 8 conflicting fields. These fields are, even without the index I deleted, present in the older index, for which filebeat-\* should have no problem accessing. Any tips on why they are now conflicted? Index Template is based on filebeat-\*. Thank you! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 7, 2020, 10:38pm UTC](https://discuss.elastic.co/t/the-data-you-are-seeing-might-be-incomplete-or-wrong/211386/2 "2020-01-07T22:38:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.