Print job statuses
| Status | Meaning | Action needed |
|---|---|---|
| Queued | Created, waiting for an agent to collect it | None, if an agent is running |
| Sent | An agent has it | None |
| Printing | Going to the printer now | None |
| Done | Printed | None |
| Error | The agent could not print it. A reason is recorded | Yes — read the reason |
Queued has two meanings
The distinction that matters most, because both look like "nothing is happening".
Queued, waiting for an agent. Normal. It prints as soon as an agent collects it — usually immediately. A build-up means no agent is running at that site.
Queued and unrouted. Yessort could not work out which printer the job should go to, so it parked the job rather than failing it. It waits until a printer is resolvable — a routing rule, or a site default.
The second is not an error and is not reported as one. Nothing went wrong; the question of where to print simply has no answer yet. See how a printer is chosen.
Error is the agent's verdict
An error means the job reached an agent and the agent could not print it — printer offline, out of labels, rejected the data.
So an error tells you the chain is working up to the last step. That is more informative than it sounds: the agent is running and collecting jobs.
What a job carries
Its document type — courier label, packing slip, pick list, product, location or licence-plate label. See print document types.
Its payload — ZPL for a thermal label printer, or PDF.
Diagnosing from the status
| What you see | Likely cause |
|---|---|
| Everything queued, nothing sent | No agent running at that site |
| One job queued, others printing | That job is unrouted — no printer matched |
| Sent, never done | The agent has it; check the printer itself |
| Error | Read the reason; the chain works up to the printer |
Fix a print that did not appear works through these in order.