Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Statuses of data indexing

Updated on May 11, 2022

The search landing page provides an option to verify the status of classes for which you index their data into the search functionality. You can analyze the index status to verify whether specific data is searchable in your application.

Statuses differ depending on your deployment.

The following table presents all possible statuses that you can encounter during data indexing.

Statuses of data index

Embedded Elasticsearch statusesSearch and Reporting Service statuses
The index is usable, and the last reindexing attempt succeeded.
The index is usable. The last reindexing attempt failed or did not occur yet.
The index is not usable.
Dedicated indexes only: The index exists in Elasticsearch cluster but no Custom Search Property uses that index.
Dedicated indexes only: The index contains obsolete mappings. Recreate the index.
The index is usable, but contains data type conflicts to fix.
Note: The system cannot identify conflicts when you make changes in the Custom Search Properties rule form.
[no status]
Full reindexing did not occur yet.
The system received a request to reindex the class, but the process is not started yet.
The system is currently indexing data. The Records indexed column displays the progress of the indexing process.
The system completed the indexing process.
The operator canceled the indexing, and the data can be incomplete.
  • Types of indexing errors

    The Search landing page displays error messages when the system encounters issues with data indexing. You can find solutions to these issues by analyzing the corresponding error messages.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us