After documents are ingested into Docupath through drag-and-drop, email, or API uploads, they enter a processing queue where the AI Model Garden extracts structured data from unstructured content. The queue manages the order and status of documents throughout their lifecycle, and users can monitor queue progress from the Review Screen. Understanding queue behaviour is essential for managing document workflows and troubleshooting processing delays.
How It Works
Document Ingestion and Queue Entry
When a document is uploaded to Docupath through any ingestion method (drag-and-drop upload, email ingestion, or API submission), it immediately enters the upload queue. The system assigns the document a unique identifier, captures its file metadata (name, size, upload timestamp), and validates that the document meets platform requirements (file type, size under 50MB, page count under 150). Documents that fail validation are rejected at upload time and do not enter the queue. Valid documents are marked as "Pending" and await processing by the AI Model Garden.
Queue Visibility on the Review Screen
The Document Queue's "Pending" tab displays all documents currently in the upload queue. The "Processing status" column shows the current state of each queued document:
Pending: Document awaiting processing; position in queue is visible through queue order.
Processing: Document is currently being processed by the AI Model Garden; this status typically lasts 30 seconds to 2 minutes depending on document complexity.
Failed: Document processing failed; see "Identifying Stuck Documents" below.
Complete: Document processing finished successfully; document moves to "Pending Review" and appears in relevant status tabs.
Users can filter the Pending tab by document type, upload date, urgency flag, and other criteria to locate specific documents in the queue. A red bubble indicator on the Pending tab shows the count of documents awaiting review.
Managing Columns
The columns shown in the Document Queue can be shown, hidden, and re-ordered. All columns can be moved into any order. Some columns are mandatory and cannot be hidden, while others are optional.
Mandatory (cannot be hidden):
Upload Time
Document Type
Primary Party Name
Document Date
File name
Optional (can be hidden):
Validated By
Secondary Party Name
Primary Party Country
Secondary Party Country
Primary Party VAT No
Secondary Party VAT No
Posting Date
Delivery Date
Due Date
Net Amount
Total Tax
Expected Processing Times
Processing time varies based on document complexity, document type, and current queue load:
Simple Documents (invoices, receipts): 30 seconds - 2 minutes from upload to processing complete
Complex Documents (contracts, multi-page statements): 1-3 minutes
Documents with Handwriting or OCR Requirements: 1-3 minutes
Peak Load Times: Processing times may extend by 50-100% during high-volume periods
Organization-level SLAs can be configured to set expected processing timeframes. Exceeded SLAs trigger alerts for Managers and Admins.
Batch Processing Behaviour
When multiple documents are uploaded as a batch (up to 100 documents per batch), they enter the queue as a group. Each document is processed sequentially in batch order. A batch upload progress indicator shows the number of documents processed versus total batch size. Users can monitor overall batch progress from the Pending tab by filtering for the batch upload timestamp or batch ID.
Queue Load and System Performance
Docupath dynamically manages queue capacity to maintain system performance. During peak load periods, the queue may temporarily hold documents in "Pending" status for longer than typical. Queue load is visible to Admins and Managers through the Organization Dashboard, which displays current queue depth and average processing time. Organizations can request queue priority adjustments through customer support if consistent queue delays occur.
Supported Configurations and Options
Configuration | Details | Queue Order | First-In, First-Out (FIFO) by default |
Urgent Priority | Documents processed within 2-5 minutes | Queue Visibility | Review Screen > Pending tab |
Status Tracking | Pending, Processing, Failed, Complete | Batch Processing | Up to 100 documents per batch; sequential processing |
Queue Depth Display | Available to Admin and Manager roles | Filtering Options | Document type, upload date, urgency, status |
Other Technical Specifications
Specification | Value | Notes |
Typical Processing Time (Simple) | 1-3 minutes | Invoices, receipts, standard documents |
Typical Processing Time (OCR) | 5-15 minutes | Handwritten content, scanned documents |
Maximum Batch Size | 100 documents | Per single batch upload |
Queue Timeout | 1 hour | Automatic retry if document stuck in queue |
Status Update Frequency | Real-time | UI updates as status changes |
Notes
Stuck Documents in Processing: If a document remains in "Processing" status for more than 1 hour, it is automatically marked as "Failed" and eligible for reprocessing. Manual intervention is not required.
Network Interruption During Upload: If a document upload is interrupted mid-transfer, the partial upload is discarded and the user must re-upload. Partial documents do not enter the queue.
Email Ingestion Delays: Documents received via email may have a 5-10 minute ingestion delay before entering the queue, depending on email server load. This delay is separate from processing time.
Batch Upload Partial Failures: If documents in a batch exceed platform limits (file size, page count), the entire batch upload may fail before any document enters the queue.
Queue Clear on Tenant Upgrade/Downgrade: Organizational tier changes may cause queue reordering. Documents maintain their identities but processing order may shift.
Processing Failure Root Causes: Failed documents may fail due to corrupted files, unsupported file formats, image quality issues (too blurry or small), or transient processing errors. The system provides limited error detail to end users; contact support for detailed failure analysis.