Skip to Content
DocumentsDocument Status

Document Status Lifecycle

Every document in Virza has a status that reflects where it is in the processing pipeline. Understanding these statuses helps you know what’s ready, what’s still being processed, and what needs attention.

Status overview

Uploading → Processing → Available → Enriching → Ready ↘ Ready with warnings ↘ Failed ↘ Infected

All document statuses

StatusWhat it meansWhat you can do
UploadingFile is being transferred to secure storage and scanned for malwareWait for upload to complete
ProcessingVirus scan passed, core extraction pipeline is running (text, metadata, sections)Wait, typically 15–30 seconds
AvailableFull text is extracted and visible. Search indexing is in progress.Read the document, view extracted text and metadata
EnrichingStructure is visible (sections, tables, figures). AI enrichment stages are running (summaries, embeddings, citations).Use the document: read, search, and view structure. AI features will appear as they complete.
ReadyAll pipeline stages completed successfullyFull access to all features
Ready with warningsCore extraction succeeded, but one or more optional stages failed (e.g., embedding provider was temporarily unavailable)Full access to core features. Some enrichment artifacts may be missing. See the document details for specifics.
FailedA critical pipeline stage failed (text extraction, section splitting, or file validation)Check the error message. Common fixes: re-upload, use a text-based PDF, remove password protection. See Failure Modes.
InfectedVirus or malware was detected during the security scanThe file has been quarantined and deleted. Upload a clean version of the document.
Metadata onlyDocument was imported without a PDF (e.g., from a citation match)View metadata only. Upload the actual PDF to enable full processing.

Per-artifact status

Each document also tracks the status of individual extraction artifacts independently:

ArtifactWhat it represents
TextFull-text extraction
SectionsSemantic section segmentation
TablesTable detection and extraction
FiguresFigure detection and cropping
CitationsReference parsing and DOI resolution
EmbeddingsVector representations for semantic search
SummaryAI-generated executive summary
MetadataTitle, authors, DOI, and other bibliographic data

Each artifact can be in one of these states:

  • Pending: waiting to run
  • Processing: currently running
  • Ready: completed successfully
  • Failed: the stage encountered an error
  • Partial: some data was extracted but the result is incomplete
  • Not triggered: this stage was skipped because it requires a higher plan tier

A document can be Ready with warnings when core artifacts (text, sections) succeeded but optional artifacts (embeddings, summary) failed. The document is fully usable. Optional artifacts can be retried from the document menu.

What triggers reprocessing

Documents are reprocessed automatically when:

  • You re-upload a new version of the file
  • A major parser upgrade is deployed (rare, you’ll see a notification)

You can also manually trigger reprocessing from the document menu (⋯ → Reprocess) if you believe extraction quality can be improved.

Last updated on