---
title: "Resume Index Operation"
url: "https://docs.ravendb.net/6.2/client-api/operations/maintenance/indexes/start-index"
version: "6.2"
language: "nodejs"
---

# Resume Index Operation

> Client language: Node.js. Also available for [C#](https://docs.ravendb.net/6.2/client-api/operations/maintenance/indexes/start-index.md), [Java](https://docs.ravendb.net/6.2/client-api/operations/maintenance/indexes/start-index.java.md), [Python](https://docs.ravendb.net/6.2/client-api/operations/maintenance/indexes/start-index.python.md), [PHP](https://docs.ravendb.net/6.2/client-api/operations/maintenance/indexes/start-index.php.md).
>
> RavenDB publishes an official agent skill for coding assistants at https://docs.ravendb.net/skills/ravendb/SKILL.md (also installable with `npx skills add ravendb/skills`). The skill describes itself as: "Read this before writing any RavenDB query, client call or /databases/ request. Covers server setup, document modelling, the Node.js, .NET and Python clients, RQL, indexes, vector search and AI agents. Code written from recall tends to run and return the wrong rows, because RQL resembles SQL and the clients take field names as plain strings."

> **Note**
>
> - After an index has been paused using [StopIndexOperation](https://docs.ravendb.net/6.2/client-api/operations/maintenance/indexes/stop-index.nodejs.md),  
>   use `StartIndexOperation` to **resume the index**.
>
> - When resuming the index from the **client**:  
>   The index is resumed on the preferred node only, and Not on all the database-group nodes.
>
> - When resuming the index from the **Studio** [indexes list](https://docs.ravendb.net/6.2/studio/database/indexes/indexes-list-view.md#indexes-list-view---actions) view:  
>   The index is resumed on the local node the browser is opened on, even if it is Not the preferred node.
>
> - In this page:
>   - [Resume index example](#resume-index-example)
>   - [Syntax](#syntax)

## Resume index example

```javascript
// Define the resume index operation, pass the index name 
const resumeIndexOp = new StartIndexOperation("Orders/Totals");

// Execute the operation by passing it to maintenance.send
await store.maintenance.send(resumeIndexOp);

// At this point:
// Index 'Orders/Totals' is resumed on the preferred node

// Can verify the index status on the preferred node by sending GetIndexingStatusOperation
const indexingStatus = await store.maintenance.send(new GetIndexingStatusOperation());

const index = indexingStatus.indexes.find(x => x.name === "Orders/Totals")
assert.strictEqual(index.status, "Running");
```

## Syntax

```javascript
// class name has "Start", but this is ok, this is the "Resume" operation
const resumeIndexOp = new StartIndexOperation(indexName);
```

| Parameters | Type | Description |
| - | - | - |
| **indexName** | `string` | Name of an index to resume |

## See also

- [What are Indexes](https://docs.ravendb.net/6.2/indexes/what-are-indexes.nodejs.md)
- [Creating and Deploying Indexes](https://docs.ravendb.net/6.2/indexes/creating-and-deploying.nodejs.md)
- [Index Administration](https://docs.ravendb.net/6.2/indexes/index-administration.md)
- [How to Disable Index](https://docs.ravendb.net/6.2/client-api/operations/maintenance/indexes/disable-index.nodejs.md)
- [How to Pause Index Until Restart](https://docs.ravendb.net/6.2/client-api/operations/maintenance/indexes/stop-index.nodejs.md)
- [Resume index from Studio](https://docs.ravendb.net/6.2/studio/database/indexes/indexes-list-view.md#indexes-list-view---actions)
