# Limits?

**URL:** <https://discuss.elastic.co/t/limits/281505>\
**Category:** Elastic Search\
**Tags:** elastic-workplace-search\
**Created:** [August 16, 2021, 6:23am UTC](https://discuss.elastic.co/t/limits/281505 "2021-08-16T06:23:51Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![catmanjan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catmanjan/32/77810_2.png) [@catmanjan](https://discuss.elastic.co/u/catmanjan)\
**Post date:** [August 16, 2021, 6:23am UTC](https://discuss.elastic.co/t/limits/281505/1 "2021-08-16T06:23:51Z")

</div>

App Search has this handy page describing the limits

> **[Limits | Elastic App Search Documentation \[8.4\] | Elastic](https://www.elastic.co/guide/en/app-search/current/limits.html)**

Do these same limits apply to Workplace Search? If not, is there a document like this explaining the limits for Workplace Search?

---

<div class="post-metadata">

**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\
**Post date:** [August 16, 2021, 3:36pm UTC](https://discuss.elastic.co/t/limits/281505/2 "2021-08-16T15:36:36Z")

</div>

Hi @catmanjan!

That's a good question. As of now, Workplace Search does not have an analogous documentation page to go over each of its configurable limits. However, if you visit [Configuration | Elastic Enterprise Search Documentation [7.14] | Elastic](https://www.elastic.co/guide/en/enterprise-search/current/configuration.html) and search for `--- Limits ---`, you'll see a section of Workplace Search limits and their descriptions.

Is that helpful? Is there a specific limit you need clarification on?

---

<div class="post-metadata">

**Author:** ![catmanjan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catmanjan/32/77810_2.png) [@catmanjan](https://discuss.elastic.co/u/catmanjan)\
**Post date:** [August 17, 2021, 12:40am UTC](https://discuss.elastic.co/t/limits/281505/3 "2021-08-17T00:40:30Z")

</div>

Thanks Sean - in this thread constanccechen says regarding Appsearch "Unfortunately the 10k results per query limit isn't configurable"

> [@How to increase query results limit of 10,000 results per search in AppSearch](https://discuss.elastic.co/t/how-to-increase-query-results-limit-of-10-000-results-per-search-in-appsearch/280770):
>
> AppSearch has a limit of max 10,000 search results per query. Is this value configurable? We have a requirement where we need to parse through all the search results for a particular filter condition, and update the resulting documents. However if we don't get the right number of results(which can be more than 10,000), we would not be able to update those documents to the right value, this could lead to data in -consistency. Is there a way to get more than 10,000 results from a search quer…

Are there any similar hard limits in Workplace Search?

---

<div class="post-metadata">

**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\
**Post date:** [August 17, 2021, 3:22pm UTC](https://discuss.elastic.co/t/limits/281505/4 "2021-08-17T15:22:18Z")

</div>

@catmanjan yes, there are similar hard limits. For example, any of our APIs that support pagination will not fetch more than 100 pages, and will not allow you to retrieve more than 100 results per page (which leads to that 10,000 result hard limit). Does that answer your question?

---

<div class="post-metadata">

**Author:** ![catmanjan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catmanjan/32/77810_2.png) [@catmanjan](https://discuss.elastic.co/u/catmanjan)\
**Post date:** [August 17, 2021, 11:16pm UTC](https://discuss.elastic.co/t/limits/281505/5 "2021-08-17T23:16:07Z")

</div>

> [@Sean\_Story](#):
>
> u to retrieve more than 100 results per page (which leads to that 10,000 result hard limit). Does that ans

Thanks, that somewhat answers my question - would it be fair to say that the limits documented in the AppSearch page also apply to Workplace Search?

---

<div class="post-metadata">

**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\
**Post date:** [August 18, 2021, 3:20pm UTC](https://discuss.elastic.co/t/limits/281505/6 "2021-08-18T15:20:58Z")

</div>

@catmanjan, it's a reasonable assumption to make, though it won't hold for every case. For example,

- Workplace Search doesn't have engine boosts, so `Boosts` does not apply
- Workplace Search external ID limit is `487` bytes, where App Search's `id Schema Field Value Length` is `800 characters`
- Workplace Search doesn't have meta engines, so `Engines per Meta Engine` does not apply

I'll capture a need for Workplace Search to provide a similar guide on its limits. In the mean time, hopefully, you'll find that our APIs are self-explaining, and that if you exceed a limit, the response will tell you what limit you exceeded and how to adjust it (if you can). If you don't find that to be the case, don't hesitate to file a support ticket or start a thread in these discuss forums.

---

<div class="post-metadata">

**Author:** ![chriscressman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chriscressman/32/93362_2.png) [@chriscressman](https://discuss.elastic.co/u/chriscressman)\
**Post date:** [August 18, 2021, 5:28pm UTC](https://discuss.elastic.co/t/limits/281505/7 "2021-08-18T17:28:19Z")

</div>

Hi @catmanjan .

Do you mind answering a few questions to help with future documentation?

Would you prefer to find these limits documented within the context in which they apply? For example, we could improve our API references and configuration settings reference to cover all limits in the context of each field, setting, or endpoint.

Or, is there distinct value in collecting all "limits" in one place within the documentation? If so, how would you describe that value?

Thank you!

---

<div class="post-metadata">

**Author:** ![catmanjan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catmanjan/32/77810_2.png) [@catmanjan](https://discuss.elastic.co/u/catmanjan)\
**Post date:** [August 18, 2021, 11:14pm UTC](https://discuss.elastic.co/t/limits/281505/8 "2021-08-18T23:14:28Z")

</div>

> [@chriscressman](#):
>
> Or, is there distinct value in collecting all "limits" in one place within the documentation? If so, how would you describe that value?

I like the way AppSearch does it - its particularly useful for developers who have to communicate the limitations to stakeholders so they can adjust their expectations.

While you could provide each limit on the page with their counterpart function, inevitably someone will ask for a collated report...

---

<div class="post-metadata">

**Author:** ![chriscressman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chriscressman/32/93362_2.png) [@chriscressman](https://discuss.elastic.co/u/chriscressman)\
**Post date:** [August 19, 2021, 4:28pm UTC](https://discuss.elastic.co/t/limits/281505/9 "2021-08-19T16:28:58Z")

</div>

Thanks for the response! I'll discuss further with the Workplace Search team.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 31, 2022, 2:48am UTC](https://discuss.elastic.co/t/limits/281505/10 "2022-10-31T02:48:05Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
