# kibana.autocompleteTerminateAfter': is not allowed **URL:** \ **Category:** Kibana\ **Created:** [December 9, 2021, 1:42am UTC](https://discuss.elastic.co/t/kibana-autocompleteterminateafter-is-not-allowed/291279 "2021-12-09T01:42:24Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![lifeowl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lifeowl/32/92530_2.png) [@lifeowl](https://discuss.elastic.co/u/lifeowl)\ **Post date:** [December 9, 2021, 1:42am UTC](https://discuss.elastic.co/t/kibana-autocompleteterminateafter-is-not-allowed/291279/1 "2021-12-09T01:42:24Z")
Hi there, Have there been any recent changes or deprecations with kibana.autocompleteTerminateAfter? I recently had this value configured in my kibana.yml file (using 7.14 on Elastic Cloud) but now, when I try to update the value, I receive the following error (no matter what value I set it to between 0 and 10000000). _kibana.autocompleteTerminateAfter': is not allowed_ **Note** : The reason I set this configuration is to remove the warning symbols that appear next to the lookup fields on my Kibana dashboards. When hovering over the icon, the following pop-up text is displayed: "_Terms list might be incomplete because the request is taking too long. Adjust the autocomplete settings in kibana.yml for complete results_". Thanks! ---
**Author:** ![dosant](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dosant/32/64489_2.png) [@dosant](https://discuss.elastic.co/u/dosant)\ **Post date:** [December 9, 2021, 2:06pm UTC](https://discuss.elastic.co/t/kibana-autocompleteterminateafter-is-not-allowed/291279/2 "2021-12-09T14:06:53Z")
Hi @lifeowl, This indeed was renamed into `data.autocomplete.valueSuggestions.terminateAfter` With the rename in Kibana we've also changed allowlisting in cloud so that `kibana.autocompleteTerminateAfter` is no longer allowed, but we made a configuration mistake and didn't allow new `data.autocomplete.valueSuggestions.terminateAfter` . This will be fixed in future cloud releases. Until this is fixed you can use old `kibana.autocompleteTerminateAfter` but only for versions before 7.14 ☹ ---
**Author:** ![lifeowl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lifeowl/32/92530_2.png) [@lifeowl](https://discuss.elastic.co/u/lifeowl)\ **Post date:** [December 11, 2021, 3:34am UTC](https://discuss.elastic.co/t/kibana-autocompleteterminateafter-is-not-allowed/291279/3 "2021-12-11T03:34:59Z")
Thanks, @dosant. I’m not necessarily seeing or feeling any performance impact in this case, but rather my client is hoping to remove the warning icons for user experience considerations. That said, is there a way to hide or remove the warning icon in my dashboard visualizations in 7.14 Elastic Cloud? I had thought about introducing some custom CSS via plugins but, in Elastic Cloud, custom plugins are limited to Gold and Enterprise account types. And I’d prefer not to downgrade as I’m leveraging some 7.14-specific features (like Fingerprint Processor). Thanks! ---
**Author:** ![lifeowl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lifeowl/32/92530_2.png) [@lifeowl](https://discuss.elastic.co/u/lifeowl)\ **Post date:** [December 12, 2021, 3:25am UTC](https://discuss.elastic.co/t/kibana-autocompleteterminateafter-is-not-allowed/291279/4 "2021-12-12T03:25:19Z")
Also, any chance that "data.autocomplete.valueSuggestions.terminateAfter" made it into 7.16.0 which is now available in Elastic Cloud? I'm seeing it now in [kibana/kibana.yml at main · elastic/kibana · GitHub](https://github.com/elastic/kibana/blob/main/config/kibana.yml). If not, do you know what release the fix is targeted for, and when it might be available (days, weeks, months)? Thanks! ---
**Author:** ![dosant](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dosant/32/64489_2.png) [@dosant](https://discuss.elastic.co/u/dosant)\ **Post date:** [December 13, 2021, 4:03pm UTC](https://discuss.elastic.co/t/kibana-autocompleteterminateafter-is-not-allowed/291279/5 "2021-12-13T16:03:33Z")
@lifeowl, sorry could not give a better ETA then a couple of weeks. If that can't wait, then I'd reach out through support channel about this instead of discuss. Support engineer should be able to force override the config through cloud console ---
**Author:** ![clibassi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/clibassi/32/92334_2.png) [@clibassi](https://discuss.elastic.co/u/clibassi)\ **Post date:** [January 5, 2022, 2:34am UTC](https://discuss.elastic.co/t/kibana-autocompleteterminateafter-is-not-allowed/291279/6 "2022-01-05T02:34:04Z")
Any updates on this? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 2, 2022, 2:34am UTC](https://discuss.elastic.co/t/kibana-autocompleteterminateafter-is-not-allowed/291279/7 "2022-02-02T02:34:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.