Held or failed files
Find out why a file is unavailable and choose the right recovery step.
Read the file result
Each file result means one of the following:
| Result | Meaning |
|---|---|
| Indexed | The searchable text is ready. An agent still needs access to the document's folder or collection. |
| Pending or converting | Processing has not finished. Check again before asking an agent to use the file. |
| Held or quarantined | The document is stored but withheld from agent retrieval. Read its reason and suggested action. |
| Refused | The upload did not create the requested document, for example because it was an exact duplicate or an unsupported type. Follow the per-file reason. |
| Failed | The upload request could not complete. Retry the failed file after checking the reported problem. |
Inspect a held document
- Open Documents and choose Held in the status filter.
- Open the file and read the hold reason and suggested action. A possible credential, sensitive content or a quality issue needs a different response from a temporary processing failure.
- Inspect the source yourself. Remove content that should not be shared and correct unreadable or incomplete text.
- Use Edit text if the complete converted text is available and the correction belongs there. Otherwise prepare a corrected source file and upload it, then remove the obsolete held copy when appropriate.
- Check that the result is Indexed before asking an agent to use it.
Do not assume a hold will clear on its own. A successful save or retry can still leave the file held if the checks find the same issue.
Know what Retry does
Retry on a document rereads the stored original with the current extractor and reruns the checks. It does not bypass a hold, and it does not upload a corrected file from your computer.
Use it after a temporary failure or when you expect reprocessing the original to help. If the original still contains the problem, correct the content first. Retrying can replace earlier edits to the converted text because the original is its input.
Read the result after retrying. If the file remains held, follow the new or repeated action shown rather than retrying in a loop.
Recover an incomplete batch
In the upload queue, Retry failed retries failed uploads. Files already marked indexed do not need to be uploaded again.
| Reason | Recovery |
|---|---|
| Duplicate | Find and use the existing document. Delete it only if you intend to replace it. |
| Unsupported or unreadable file | Export the source into a supported format and check that it contains readable text. |
| File too large | Split or reduce it before uploading again. |
| Authentication or rate-limit error | Resolve the session or limit first. Repeating the same batch immediately will not fix it. |
| Blocked by network security | The hosting filter flagged the file before it reached Takibi — command-like text is the usual trigger. Reword it and upload again; identical bytes always trip the filter. |
See Usage & troubleshooting for request errors and budgets.