Upload failed, or AIRI loci did not read a file
TroubleshootingReview draft
On this page
Distinguish a failed upload from processing in progress or an incorrect reference. A filename or thumbnail alone does not prove that AIRI loci Agent has read the content.
| Message or symptom | What to do |
|---|---|
| Unsupported file type | Export a supported format from the original application; do not just rename the extension. |
| File too large | Compress or split it and upload the relevant part. |
| Too many files or batch too large | Upload in smaller batches and keep successful uploads. |
| Image too small or too many pixels | Export a legible version within the size limits. |
| Video too long or resolution too high | Trim the relevant segment or adjust resolution. |
| Unreadable file | Check that it opens locally, then export it again. |
| Storage full | Resolve workspace capacity; retrying cannot remove the limit. |
| Content not allowed | Review the message and materials. Report a suspected incorrect decision. |
Upload finished, but sending is blocked
Wait for processing. Check that the current task accepts the attachment type, count, and combination. Support for uploading a format does not mean every generation model accepts it as input.
You can send, but the answer ignores the file
Check that the file is actually attached to this draft and that the reference points to the right material. Reference it again and specify a page, table, or region and a concrete reading goal.
Scans, complex tables, and blurry text may be read incompletely. Supply a clear image or paste key text and ask for another check. A confident answer is not proof that the entire file was read.
When only part of a batch fails, keep the successful files and resolve the failures individually.
Upload limits · Referencing attachments · Storage full · Documentation