Search API Breaking Change
Currently Search API queries do not have an enforced cap on the number of results returned. This can lead to timeouts and 500 errors when the page requested includes a result beyond 200k records. On Thursday, June 16, once a query requests a page past the limit (e.g. ?page=2001), a 422 (Insufficient Resource Error) will be returned to signify that there are too many result for the query.
This limit will help maintain a reasonable load on database queries and provide a better user experience. In situations where large queries need to be made, we recommend serializing the data in smaller chunks by limiting results to a specific date range. Alternatively, if exporting and warehousing large amounts of data then using one of our Incremental Export endpoints is more appropriate. An example of how this can be accomplished is found below.
- Note: A query that might yield too many results is found highlighted in red. An example that shows how to constrain the query is found highlighted in green.
type:tickets tags: group_a created_at>2016-01-01 created_at<2014-02-01
If you make use of the Search API and are making queries with over 200k results, you will receive a 422 Error response code.