There are multiple locations where you can examine the reason behind indexing errors:
The Error log in Review Manager
The Alerts panel in Reveal Web’s Document Viewer
Review Manager – Index Errors log
To examine the indexing log for the current or previous jobs in a project, click Create > Indexes > View log. This will open up the Index Errors tab. The log in this tab displays which document text sets errored during indexing.
Errors table
Common index errors are represented in the below table, including descriptions.
Error | Description |
|---|---|
Not Defined | The path to the OCR or native is missing. For third party loads, check load file paths. |
Missing | The native was not found. |
Too large | The file is larger than the size limits set within the Text Set settings. It’s recommended to download and view these files natively. |
Empty Source | The file is empty, so it has no content to extract or convert. |
Convert Empty | Conversion of native was successful, but there was no output text. |
Insert Failures | There was a failure when attempting to add the document’s text to the Elastic Index. |
File contains no usable text | Includes non-text searchable files, i.e. non text searchable PDFs or image based files. |
File Conversion is not supported | The source file was not found during indexing. |
File type is not supported | A typical error when running Spreadsheet View index on non-excel file types. |
Unknown Exception: 4 | Rarely seen, usually linked to the Extracted text set index where the document contains no indexable text. |
Reveal Web – Alert details in Document Viewer
In the Document Viewer sidebar, an Alerts panel will be visible if your document encountered an indexing error. The only errors represented in this panel are indexing errors.
Searching for documents with alerts
There are two filters that can help you filter your Review Grid to documents with alerts.
Has Alert field
The Has Alert field is a y / n field that marks whether or not your document has an alert, regardless of what type the alert is.
Note
Make sure you’re using the Has Alert field, and not the Has Alerts (plural) field.
Alert Detail field
The Alert Detail field is a multi-value field that displays which indexing alerts a document was flagged for in the format “[text set]: [indexing error]”. You can search for documents with specific indexing alerts for quality control checks and troubleshooting.
Important
The Alert Detail field is organized by text set and by alert. For example, to see all files with “document contains no indexable text”, you’ll need to make sure you select all text sets types from your list with that specific error (e.g. Extracted, Native View PDF, and OCR / Loaded in the below image).
See the Alert Details section for common Alert Detail errors.
Alerts table
Common alerts are represented in the below table, including descriptions.
Alert | Description |
|---|---|
Document contains no indexable text | The document exists in the project, but no searchable text could be extracted during indexing. Common reasons include non-text searchable PDFs, image based files, 0KB files, corruption, or encryption. |
Source file was too large to index | The file is larger than the size limits set within the Text Set settings. It’s recommended to download and view these files natively. |
Source file not found during index | The source file could not be located or accessed during indexing. The most common reason is incorrect file paths. As a result, it’s text could not be extracted for searching purposes. |
Annotations removed during bulk re-image | If annotations were applied to the Image view, a bulk re-image will override these annotations if the below settings are checked when submitting the image job.
|
.png)