Skip to main content

Document Error Codes

When a document fails or is skipped during ingestion, its status carries one or more error codes in the error_codes field (returned by the ingestion API and shown in the platform). Each code explains why a document did not end up indexed.

Transient problems are retried automatically and are not given a specific code; a code is recorded when a document reaches a terminal outcome. A document can carry more than one code.

Codes​

CodeNameWhat it meansWhat to do
DR000unknownThe document failed for a reason that could not be determined.Retry the document; if it persists, contact support.
DR001deletedThe document was removed. This is a lifecycle state, not a failure.Nothing.
DR002failed_processingThe document failed during processing without a more specific cause, often a transient problem that did not recover.Retry the document; if it persists, contact support.
DR003file_size_exceededThe file is larger than the maximum allowed size and was skipped.Reduce the file size, or split it into smaller documents.
DR004mimetype_mismatchThe file's declared type does not match its actual content, so it was skipped.Check the file and the content type you declared for it.
DR005file_quarantinedA malware scan flagged the file. It was quarantined and not indexed.Verify the file is safe; re-upload a clean copy.
DR006processing_timeoutProcessing the document took too long and was stopped. Usually a very large or complex file.Simplify or split the document, then re-ingest.
DR007resource_limit_exceededProcessing the document needed more memory than allowed and was stopped. Usually a very large file.Reduce the file size, or split it, then re-ingest.
DR008empty_documentNo indexable content could be extracted (for example a blank page).Confirm the document has extractable information, then re-upload.
DR009missing_required_fieldsA field required to index the document was missing.Check the document's metadata against your index schema.
DR010malformed_documentThe file could not be read because it is corrupt or not a valid file of its declared type.Re-export or re-save the file, then re-upload.
DR011protected_documentThe file is password-protected, encrypted, or rights-protected and could not be opened.Remove the protection and re-upload.
DR012workflow_not_foundThe ingestion workflow configured for this document does not exist.Configuration issue; contact your administrator.
DR013misconfigured_workflowThe ingestion workflow ran but did not produce the expected output.Configuration issue; contact your administrator.
DR014image_too_largeAn image in the document was too large to process safely.Reduce the image resolution or size, then re-ingest.
DR015content_filteredAn AI-powered processing step could not run because the model provider's content filter blocked the document's content.A terminal outcome for that step; retrying will not change it. If you believe it is in error, contact support.
DR016download_failedThe file could not be downloaded from its source (for example the source returned 403 Forbidden or 404 Not Found).Check that the source URL is reachable and that the credentials or permissions allow access, then re-ingest.

By outcome:

  • Not a failure: deleted.
  • Skipped before processing (the document is reported as skipped or quarantined): file_size_exceeded, mimetype_mismatch, file_quarantined.
  • Failed during processing (the document is reported as failed): everything else, including the unknown and failed_processing catch-alls.

New codes may be added over time. Treat any code you do not recognize as unknown.

Enhancement requests​

Document enhancement requests use a parallel set of codes prefixed DE. The failure categories mirror the document codes above one-to-one (empty_document, missing_required_fields, malformed_document, protected_document, workflow_not_found, misconfigured_workflow, image_too_large, processing_timeout, resource_limit_exceeded, content_filtered, download_failed), plus two that are specific to enhancements: noningestable and deleted.