

Before you can begin searching short message data, you must build a search index. The index enables you to perform more complex searches on RSMF documents processed in Relativity. It provides enhanced accuracy by storing and searching on the message-level and event-level metadata by using Elasticsearch.
Once the index is built, you can begin using the short message search feature. For more information on searching short message metadata, see Using short message search.
See related pages:
While Elasticsearch is similar to dtSearch and filtering, there are differences:
Search type | Description | Example | Search precision |
---|---|---|---|
Elasticsearch | Searches on message-level and event-level metadata. |
If you enter a keyword without writing a field-specific query, Relativity searches all message-level fields, including the message body. Searching for "John" returns results that match that term everywhere Relativity finds it. Such as in the Sender Display Name and Message Body fields. |
High |
dtSearch | Searches cannot search specific aspects. | If you searched "John Smith," the results would show that the phrase "John Smith" appears in the document, but not if John specifically sent a message, reacted, left the chat, and so forth. |
Medium |
Filter | Searches on document-level fields only. | If you want to find documents that have a message sent by John Smith, the closest you can get is by checking the Participants field. The Participants field tells you if John Smith was in the DM or channel at any point in time. | Low |
The Search AI app must be installed in your workspace before using short message search index.
The Search AI app is now installed in your workspace. You can begin building an index.
To build the full index, perform the following steps:
All RSMF documents processed in Relativity before May 8, 2025 must be republished before building the full index.
The Status field shows Completed when the build finishes successfully. The build process includes all RSMF documents in the workspace, so you do not have to select a saved search or specific indexed fields.
Below are the possible statuses when building a short message index:
After the full index build is complete, you can run incremental index builds as needed instead of performing full builds. For more information, see Running incremental index builds.
Refer to Using short message search to start searching on the index results from the Documents list.
After a full index build is completed, incremental builds can be performed. Incremental builds process only new RSMF documents added to the workspace and incorporate them into the index. Therefore, incremental builds typically require less time than a full build.
Consider the following items when running an incremental build:
To start an incremental build:
The Index Manager Agent will start indexing the job as soon as it becomes available in the queue.
Upon successful completion, the newly indexed files merge with the existing search index. If the job is unsuccessful, click Retry Errors located in the Errors and Details console. For more information, see Retry errors.
An automated workflow can be configured to trigger an incremental index build when new documents are added to a workspace.
To set up the automated workflow:
When errors occur, you can first try to rebuild the index with the errored documents using the Retry Errors option in the Errors and Details console. This may resolve any system issues that have occurred, allowing the errored documents to index successfully.
If there are still errors, click the Show document errors link to review each document and error. Error categories include:
You can export the document information to a .csv file using the Export link. Then, either create a saved search to exclude the documents or proceed with reprocessing them.
To view and retry index build errors, use the options in the Errors and Details console:
An event is triggered when a change is made to any of the fields below using message-level coding in the Viewer.
Their data is automatically refreshed in the index. Events are searchable shortly after the time displayed in the "Last updated on" column of the Index list, so there is no need to build an index.
If an event fails to index, the index status becomes Completed, Eventing active with errors. Click the Show Document Errors link to review the documents in the Errored Documents modal. Then, click Retry Errors to start fixing the issue. For more information, see Retry errors.
Also, if one or more message-level coding decisions did not index, a banner displays on the Documents list page. Navigate to the index details page to retry the documents.
Why was this not helpful?
Check one that applies.
Thank you for your feedback.
Want to tell us more?
Great!