If your sorting or overall ranking seems incorrect or stops working, there are a couple of things to check.
Sorting or ranking beyond the 1,000th hit
Algolia limits how many results can be accessed through pagination with the paginationLimitedTo setting (default: 1,000). Beyond the 1,000th hit:
Records might not be accessible at all, depending on your
paginationLimitedTovalue.Sorting or ranking beyond the 1,000th hit isn’t guaranteed, even if you increase
paginationLimitedTo.
If your sorting or ranking “breaks” or looks inconsistent past the 1,000th result, this limit is likely the reason.
Sorting not working before the 1,000th hit
If sorting doesn’t work within the first 1,000 hits, make sure you’ve correctly configured sorting by attribute using a replica index, following the steps for your use case:
General attribute sorting (for numeric or boolean attributes):
Follow the steps in the Sort by attribute guide to create a replica index and configure the sorting attribute.Sorting by date:
Follow the Sort an index by date guide to convert dates to Unix timestamps and configure a replica index that sorts chronologically.
Incorrect or missing replica configuration, or attempting to sort directly on string dates or unsupported attribute types, will result in sorting that appears not to work.
Ranking not working before the 1,000th hit
Review your ranking criteria and determine on which of the eight ranking criteria ranking isn't working as expected. If your ranking is breaking on a custom ranking attribute, review the custom ranking documentation. Use this guide to evaluate the problematic criteria.