Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Checking search index status

Updated on April 5, 2022

You can check the status of your index files to see whether they are complete, ready to be used, and enabled for search. This information is useful for troubleshooting and can help you determine whether to reindex the file.

Before you begin: To access the Search landing page, you must have the pxAccessSearchLP privilege, which is included in the PegaRULES:SysAdm4 role.
  1. In the header of Dev Studio, click ConfigureSystemSettingsSearch.
  2. In the Search indexing section, click the type of index for which you want to view the status: Default, Dedicated, or Custom. For information about the types of indexes, see Configuring full-text search.
  3. Review the status and statistics in each index's row. Indexes can have a status of:
    The index is usable, and the last reindexing attempt was successful.
    The index is usable; however, the last reindexing attempt was either unsuccessful or has not yet happened.
    The index is not usable; it is either corrupt or in some other unusable state.
    Dedicated indexes only: The index exists in Elasticsearch cluster but no Custom Search Property uses that index.
    Applies only to dedicated indexes. The index has obsolete mappings and must be re-created.
    The index is usable, but it has data type conflicts that need to be fixed. On the corresponding Custom Search Properties instance, click Check Conflicts.

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