Skip to main content

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

Types of indexing errors

Updated on May 11, 2022

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.

The system indicates issues with indexing of specific classes by displaying a warning icon in the Status column. You can view detailed descriptions of the issues by clicking the icon.

The following table presents the error types that you can encounter during data indexing:

Error types

CategorySystem messagePossible reason
ConnectionConnectivity problems to the service or network issues, try to reindex again, or contact the support if the problem persists.
  • Socket errors, such as a broken pipe.
  • Invalid URL to the service.
  • Network issues.
AuthenticationAuthentication failed while connecting to the service, try to reindex again, or contact the support if the problem persists.Search and Reporting Service (SRS) does not accept the JSON Web Token (JWT) that Pega Platform provides.
DatabaseFailed to read instance data from Pega database, please contact support.
  • Failed database connection.
  • Invalid database table definition.
  • Other problems with reading the instance from the database.
StorageThe service reported a problem while indexing the data, please collect the logs and contact the support.SRS encounters issues while indexing data. You can view the details in broken queue items. This type of issue requires an investigation by the SRS team.
Indexed dataSome instances could not be indexed: instance too large, or data not indexable. Consider excluding problematic classes or properties from Relevant Records and/or Custom Search Properties and reindex again.
  • The indexing request exceeds 10 MB, which due to network limitations is the maximum allowed request size.
  • SRS rejects data because of an invalid file format, or a bug in the customer application (for example, empty values for key properties).
ClassdefBad class definition detected: incorrectly imported application or corrupted database structure. Please fix the issues and try to reindex again.The indexer cannot read class definitions from the database, and so data indexing is not possible. The root cause is outside of the indexer.
Data modelData model mismatch detected. Check if the most recent data model is published and try to reindex again.Indicates conflicts between the existing property mappings and newly indexed data. This error triggers the PEGA0124 alert.
Note: You can view a more detailed description of the issue in the Data model section on the Search landing page.
InternalUnknown indexer issue, please collect the logs and contact the support.Includes exceptions that do not match any other category.

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