Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.meilisearch.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

By default, Meilisearch returns a list of 20 tasks for each request when you query the get tasks endpoint. This guide shows you how to navigate the task list using query parameters.
Paginating batches with the /batches route follows the same rules as paginating tasks.

​
Configuring the number of returned tasks

Use the limit parameter to change the number of returned tasks: 
curl \
  -X GET 'MEILISEARCH_URL/tasks?limit=2&from=10
Meilisearch will return a batch of tasks. Each batch of returned tasks is often called a “page” of tasks, and the size of that page is determined by limit: 
{
  "results": [
    …
  ],
  "total": 50,
  "limit": 2,
  "from": 10,
  "next": 8
}
It is possible none of the returned tasks are the ones you are looking for. In that case, you will need to use the get all tasks request response to navigate the results. Use the next value included in the response to your previous query together with from to fetch the next set of results: 
curl \
  -X GET 'MEILISEARCH_URL/tasks?limit=2&from=8
This will return a new batch of tasks: 
{
  "results": [
    …
  ],
  "total": 50,
  "limit": 2,
  "from": 8,
  "next": 6
}
When the value of next is null, you have reached the final set of results.
Use from and limit together with task filtering parameters to navigate filtered task lists.

​
Deleting tasks from the database

Use the delete tasks endpoint to remove tasks from the database based on uid, status, type, indexUid, canceledBy, or date.
You can only delete finished tasks (succeeded, failed, or canceled). enqueued and processing tasks cannot be deleted: cancel them first using the cancel tasks endpoint.
Task deletion is an atomic transaction: either all matched tasks are successfully deleted, or none are.

​
Automatic task cleanup

Meilisearch stores up to 1 million tasks in the task database. If enqueuing a new task would exceed this limit, Meilisearch automatically attempts to delete the oldest 100,000 finished tasks to make room. If there are no finished tasks in the database, Meilisearch does not delete anything and enqueues the new task as usual. This automatic cleanup keeps the task database bounded without interrupting ongoing work.

​
Next steps

Filter tasks

Use query parameters to filter tasks by status, type, and more.

Monitor tasks

Check the status of asynchronous operations in real time.

Asynchronous operations

Understand how Meilisearch processes tasks in the background.