Meilisearch Documents Not Showing Up

How to fix it

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

1. 1. Check the task result

   Copy steps
   1. Call GET /tasks/{taskUid} from the response of your add request
   2. If status is failed, read the error code and message
   3. Fix the document and resend the whole batch
   Did this fix it? Yes No

2. 2. Fix ids

   Copy steps
   1. An id must be an integer or a string with only letters, digits, hyphens and underscores
   2. Every document needs the primary key attribute (missing_document_id otherwise)
   Did this fix it? Yes No

3. 3. Check format and index

   Copy steps
   1. Send JSON, CSV or NDJSON with a matching Content-Type header
   2. Confirm the index uid with GET /indexes
   3. Wait until the task is succeeded before searching
   Did this fix it? Yes No

Symptoms

You added documents but search returns nothing and the index has fewer documents than expected.

Why it happens

• The task failed (a batch with one invalid or missing id is rejected entirely)
• The task is still enqueued or processing
• Wrong index uid or wrong Content-Type
• Documents were sent with a different primary key than the index uses

This guide also covers

• meilisearch documents not showing
• meilisearch documents not indexed
• meilisearch add documents no results

The same problem in other apps

All missing or lost data guides →

• Typesense Search Returning No Results or Missing Typos (Typesense)
• Algolia Updates Not Showing in Search Results (Algolia)

Other Meilisearch errors

• Meilisearch Tasks Stuck on Enqueued
• Meilisearch Indexing Slow
• Meilisearch Primary Key Error
• Meilisearch Filter Not Working (Attribute Not Filterable)
• Meilisearch Invalid API Key / Missing Authorization Header
• Meilisearch Database Version Incompatible After Upgrade
• Meilisearch Disk Usage Keeps Growing / No Space Left on Device
• Meilisearch High Memory Usage