Algolia Record Quota Exceeded or Limit Reached

How to fix it

Try these in order — the most common fix is first.

1. 1. Find what counts

   Copy steps
   1. Open the dashboard Indices page and sort by records
   2. Delete unused test and staging indices
   Did this fix it? Yes No

2. 2. Reduce records

   Copy steps
   1. Do not index one record per variant if one is enough
   2. Use fewer, larger chunks when splitting content
   3. Check your crawler config for duplicate URLs
   Did this fix it? Yes No

3. 3. Review the plan

   Copy steps
   1. Check current usage on the Billing page against your plan's included records and search requests
   2. Records are billed on the maximum reached above your plan limit, so avoid temporary spikes from reindexing
   Did this fix it? Yes No

Symptoms

Indexing fails with a record quota message, the crawler stops, or your bill jumps after growth.

Why it happens

• More records than your plan includes (the Free plan lists 50K records, Grow 100K)
• Each variant, language or chunk counted as a separate record
• Old test indices and replicas still counting
• Crawler or split-record settings that multiply records

This guide also covers

• algolia record quota exceeded
• algolia limit reached
• algolia free plan limit

The same problem in other apps

All plan limits, paywalls & watermarks guides →

• Elasticsearch Disk Watermark: Index Read-Only (FORBIDDEN/12) (Elasticsearch)

Other Algolia errors

• Algolia Search Returns No Results
• Algolia Search Results Irrelevant or Wrong Order
• Algolia 429 Too Many Requests Error
• Algolia Record Is Too Big Error
• Algolia Invalid Application ID or API Key (403)
• Algolia Updates Not Showing in Search Results
• Algolia Search Slow or High Latency
• Algolia Crawler Not Indexing Records