Document History (Document module → History) records every document-processing job you have run — parsing, extraction and classification — organised into cases. A case is one job: the files you gave, the settings used, and the results produced.
What a case record contains
Open a case from the history list to see:
| Element | What it shows |
|---|---|
| Case summary | Name/identifier, date, who ran it, and which operation (parse / extract / classify) it was. |
| Documents | The files included, each with its own status — pending, processing, complete, failed. |
| Results | Parsed content, extracted field values, or assigned categories, per document. |
| Downloads | Structured outputs available for export (for example extracted data tables). |
| Errors | Failure reasons per document, so a bad scan can be re-supplied without redoing the whole batch. |
Common tasks
- Find an earlier result — open the case and view or download the output rather than re-processing.
- Re-run after a correction — if a document failed (unreadable scan, unsupported file), fix the file and run it again; the case history keeps the original attempt for comparison.
- Track progress of large jobs — long batches process file-by-file; the per-document status tells you what is left.
- Audit what happened — history shows who processed which documents and when. Combine with Usage for the wider activity picture.
Housekeeping
- Cases accumulate; where your permissions allow, remove cases whose outputs you no longer need — after exporting anything you must retain for compliance.
- Knowledge-base content lives separately from history: deleting a case does not delete documents already imported into a knowledge base.
Related
- Document Parser · Data Extraction · Document Classification
- Workflow History — for documents processed inside automations