Managing Distribution Entries
Distribution Entries are documents in the distribution queue. This page explains how to view, interpret, and handle them.
Distribution Entry statuses
| Status | Description |
|---|---|
| Pending | Waiting for processing by the Job Queue |
| Queued | Marked for processing |
| Processing | Being evaluated |
| Distributed | Successfully forwarded |
| Failed | Distribution error - needs manual review |
Automatic distribution
- Runs via Job Queue Document Inbound - Document Distributor Bot (recommended every 20 minutes)
- Batch size: up to 30 entries per run
- Flow: Pending → Queued → Processing → Distributed; on error → Failed
Tip
While processing runs in the background you can open the Distribution Entry list and reset entries that are queued to stop further processing.
Manual distribution
Manual actions
- Distribute Manually: Choose target company + target inbound list, then distribute
- Force Distribution: Immediate rule evaluation without the wizard. For multiple entries a background session is started to process them.
- Reset Status: Failed → Pending (process again)
- Remove: Select entries and delete them
Key fields (short)
- Status: Pending / Queued / Processing / Distributed / Failed
- Original Filename, Email Subject, Email Address: Source context
- Barcode: If present, usable for rules
- Target Company: Where it was/will be distributed
- Distributed At: Timestamp on success
Error handling
Failed distributions
If status is "Failed":
Select the entry and use the log panel on the right-hand side to see error details.
Common causes: No matching rule, target list missing, permission issues, Smart Processing error
Fixes: Adjust rules or verify target, optionally Distribute Manually, then Reset Status and process again
Session issues
Problem: Entries stay in "Queued"
Solution: Check the Job Queue; if stuck, Reset Status and process again
Best practices
- Error monitoring: Review failed entries daily
- Job Queue: Ensure it stays active
- Testing: Test new rules with manual uploads
Tip
BLOB data is deleted automatically after successful distribution to free space. Remaining entries act as a log and can be removed if needed.