Algolia Crawler Not Indexing Records

How to fix it

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

1. 1. Read the crawl status

   Copy steps
   1. Open the Crawler dashboard and check whether status is Failed in the Indexing category
   2. Read the error messages
   Did this fix it? Yes No

2. 2. Fix limits

   Copy steps
   1. Use helpers.splitContentIntoRecords to cut record size
   2. Reduce record count or upgrade the plan
   Did this fix it? Yes No

3. 3. Check configuration

   Copy steps
   1. Review your extraction actions
   2. Make sure appId matches the Algolia application and apiKey has the needed ACL and no blocking index restrictions
   Did this fix it? Yes No

Symptoms

The Algolia Crawler finishes or fails but the index has no or missing records.

Why it happens

• Records exceed plan size or count limits ("Record too big", "record quota exceeded")
• Extraction actions not configured correctly
• appId does not match the Crawler add-on application
• apiKey lacks the required ACL or has index restrictions

This guide also covers

• algolia crawler not indexing
• algolia crawler no records
• algolia crawler failed

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 Record Quota Exceeded or Limit Reached
• Algolia Invalid Application ID or API Key (403)
• Algolia Updates Not Showing in Search Results
• Algolia Search Slow or High Latency