# Processing Errors Some steps in the pipeline may abort with an error. In those cases, the item is tagged with a _Processing Error_ keyword. The table below lists all the processing error codes. | | | | | --- | --- | --- | | Processing Error | Step | Description | | SQ-04102 | [Content Extraction](pipeline-steps/enrich/content-extraction.md#pipeline-steps-content-extraction) | Unsupported MIME type. The MIME type of the document is not supported, so no textual information can be extracted from the document. | | SQ-04104 | [Content Augmentation](pipeline-steps/enrich/content-augmentation.md#pipeline-steps-content-augmentation) | Unable to fetch content. The content of the item’s `link` could not be fetched as part of the content augmentation. | | SQ-05102 | [Content Extraction](pipeline-steps/enrich/content-extraction.md#pipeline-steps-content-extraction) | Unable to convert content. This is used as the generic fallback error when an unknown error happened. | | SQ-05103 | [Content Extraction](pipeline-steps/enrich/content-extraction.md#pipeline-steps-content-extraction) | Unable to parse content. The file was parsed, but did not return any content. This is usually due to a corrupt file. | | SQ-05105 | [Content Extraction](pipeline-steps/enrich/content-extraction.md#pipeline-steps-content-extraction) | Unable to convert content, document too large. Larger documents can be supported by raising the memory limit of the content conversion step. | | SQ-05106 | [Content Extraction](pipeline-steps/enrich/content-extraction.md#pipeline-steps-content-extraction) | Unable to convert content, decryption error. This usually happens with encrypted PDF documents, which can not be parsed. | | SQ-05107 | [PDF Conversion](pipeline-steps/enrich/pdf-conversion.md#pipeline-steps-pdf-conversion) | Unable to convert to PDF. This occurs when the PDF Conversion step is configured with `ignore_errors: True` and fails to convert the item to PDF. |