When a file is imported, you receive an email confirming whether the import was successful or encountered a problem. The email contains a report attachment with information about the import.
This article explains the information shown in the ‘Notes’ column of the import report.
Please note: This article related to importing MS Word and PDF specs via the 'Import unstructured documents' route.
Warnings
Warnings do not block the import. The specification can still be created, but some files were skipped. The user is notified via a report.
User dependent
User-dependent warnings can be checked and either ignored or corrected before retrying the import.
| Report message | Description |
| Unsupported file type: <ext> | A file inside the ZIP is not a supported format. Only Word (.docx), PDF, and XML files are accepted. .doc, .txt, and .rtf files are not supported. |
| <File/Zip file> size <X>MB exceeds <limit>MB limit | A file inside the ZIP, or the ZIP itself, exceeds the allowed size limit. |
| Maximum recursion level 10 reached | The ZIP contains ZIPs inside ZIPs beyond the allowed nesting depth. The innermost archives are skipped. |
| ZIP file is empty | The ZIP archive was opened successfully, but it contains no files. |
| Invalid or unsafe path: <path> | A file inside the ZIP has an unsafe or invalid path (e.g. path traversal characters). The file is skipped for security reasons. |
| Failed to open zip: Invalid zip format | The ZIP file is corrupted, incomplete, or not a real ZIP archive. |
Errors
Scenarios that block the import. The specification cannot be created. The user receives a failure report.
User dependent
User-dependent errors must be corrected before retrying the import.
| Report message | Description |
| No files were extracted from ZIP file | All files inside the ZIP failed validation, leaving nothing to import. This is the primary cause of import failure from a ZIP. |
| No sections found in document | The AI processed the document, but no specification sections could be identified, typically because it was blank, had an unrecognised structure, or did not resemble a specification. |
| details: Cannot read properties of undefined (reading 'attribute') | This issue is caused by the file's encoding. Try resaving the file in MS Word as a new .docx and reimporting. |
System dependant
System-dependent errors point to a problem with the platform. Retry the import, and if the issue continues, please contact Customer Support.
| Report message | Description |
| Error downloading file from S3: <reason> | The file could not be downloaded from storage due to infrastructure issues, missing permissions, or the file not existing. |
| Failed to upload any files from ZIP: <filename> | Files were extracted from the ZIP, but none could be uploaded to storage due to infrastructure or permissions issues. |
| Invalid or missing metadata in S3 object | Required file metadata is absent. Indicates a pipeline configuration problem. |
| <field> is missing in S3 object metadata | One or more required fields (Specification ID, Content Set ID, Organisation ID, User ID) are missing from the file metadata. Indicates a pipeline configuration problem. |
| <field> is missing in S3 object metadata | The document could not be sent to the AI service due to service unavailability, rate limiting, or authentication issues. |
| Failed to retrieve file from OpenAI: <reason> | The document was uploaded to the AI service, but could not be confirmed as accessible before processing. |
| Failed to analyze document with OpenAI: <reason> | The AI service failed to analyse the document. Caused by service errors, timeouts, or rate limiting. |
| Incomplete response: max_output_tokens limit reached | The AI response was cut off because the document is too large or complex for a single processing call. |
| Missing parsed output from OpenAI | The AI response was cut off because the document is too large or complex for a single processing call. |
| <GraphQL error from Chorus API> | The extracted content could not be saved to the specified format due to API errors or authentication failures. |