Print queue
One queue for every
3D print job.
Bring submitted, waiting, printing, failed, and completed work into one view. Requesters follow their own jobs while operators manage the exceptions.
What is a 3D printing queue?
A 3D printing queue is the list of jobs waiting to be printed. For a fleet, that list also needs to know which printers and materials can run each job, which work is blocked, and what should happen next.
A shared queue gives operators one operating view instead of a separate plan for every machine. Its queue discipline sets the normal order, while rules, permissions, and job history make exceptions visible rather than informal.
Shared print queue · 6 jobs · 4 printers
Est. clear: 9h 40m
- 1Printing
S. Tan
housing_final.3mf
- 2Printing
A. Reyes
gear_assembly.3mf
- 3Priority
M. Lewis
fixture_a.3mf
- 4Queued
C. Wong
enclosure.3mf
- 5Queued
J. Kerr
bracket_v3.3mf
- —On hold
Prusa MK4 · #05
Belt service · 340h
Illustrative view of a shared queue across a mixed fleet.
The problem
Where manual queues start costing time.
The printer list, the job list, and the material list drift apart. Keeping them reconciled becomes work of its own.
Per-machine queues go stale
A list for each printer makes every outage or material change a manual rescheduling problem. The operator has to keep all of those lists consistent.
Invisible queues aren't trusted
If requesters can't see the status of their own work, they'll ask someone who can. That turns ordinary status checks into an operator's daily workload.
Idle gaps eat capacity
A printer can be technically available while no work reaches it. Tracking the gap between jobs shows how much time is being lost to dispatch and handoff.
How it works
From submission to recorded outcome.
Five stages, each of which produces the record the next one depends on.
- 1
A job enters the queue
A requester uploads a sliced print file. Pluraprint parses its printer model, duration, and material requirements, then adds any project fields your deployment asks for.
- 2
The job clears its requirements
Rules and quotas determine what has to happen before the job can queue. Approvals can be assigned to specific roles, and each decision is recorded on the job.
- 3
The queue orders it
Ready jobs share one queue. Rules can assign priority, and operators with permission can prioritize or deprioritize work when circumstances change.
- 4
The job is dispatched
Pluraprint checks the job against the current printer and material state before sending it. Dispatch keeps separate track of work that started, did not start, or has an uncertain outcome.
- 5
Everyone sees the outcome
The requester can follow the job through printing, completion, failure, reprint, and pickup. Its history remains available for as long as the deployment's retention policy keeps it.
Queue capabilities
What the queue keeps connected.
Job order is one piece. The queue also has to carry requirements, printer state, decisions, failures, and requester-visible status.
One shared queue
Ready work stays in one place instead of being split across private spreadsheets, inboxes, and machine-specific lists.
Automatic job routing
Dispatch checks the job's printer model and material requirements against the machines that are available to its site.
Live queue position
Requesters can see the current state of their own jobs, so a routine status check doesn't have to become a message to an operator.
Queue priority
Rules can assign priority, and operators can adjust queued work when a deadline or production issue calls for it.
Batches and repeats
Create related work without losing the source job and its material or print settings.
Maintenance holds
Mark a printer down for service so it isn't treated as available for new work. Existing jobs remain visible in the queue.
Failure handling
Record the failed outcome on the original job, notify the requester, and create another attempt without rebuilding the submission.
Queue analytics
Use throughput, idle time, quality, and failure data to see where queued work is losing time.
Job and audit history
Keep the submission, checklist decisions, dispatch attempts, events, and final outcome attached to the same job.
Queue discipline
Make the normal order clear.
The rule that decides order is called queue discipline. A visible default gives operators room to handle exceptions without making the whole queue feel arbitrary.
First-come, first-served
Jobs run in submission order. It's easy to explain and often a good starting point for shared labs and teaching spaces.
Priority
Higher-priority work moves first. Use it for real deadlines and make sure operators can see why the order changed.
Fair share
Quotas can limit how many active jobs one person holds, which keeps a few heavy users from filling the queue.
Printer eligibility
Printer model, site, and material requirements narrow the set of machines that can receive a job.
Who runs a queue
Different operations, same queue.
Makerspaces & teaching labs
Many requesters share a limited number of machines. Visible job status and clear approval rules reduce routine coordination work.
Learn more →Production print farms
Production work needs priorities, repeatable job records, and a clear view of throughput and failure.
Learn more →Research & R&D labs
Sensitive work needs controlled access and enough job history to explain what was printed, by whom, and on which machine.
Learn more →Questions
3D printing queue FAQ
The questions operators ask before they change how their queue works.
What is a 3D printing queue?
A 3D printing queue is the list of jobs waiting to run across a group of printers. A shared queue keeps job order, requirements, status, and printer assignment together instead of maintaining a separate list for each machine.
What is 3D print queue software?
3D print queue software manages how jobs enter the operation, what must happen before they can print, how they are ordered, and which printer receives them. It also keeps the requester-visible status and job history in one place.
How does Pluraprint decide which printer runs a job?
Pluraprint checks the job's site, printer model, material requirements, and the current machine state at dispatch. Operators can change job priority or mark a printer down when the floor changes.
Can requesters see their position in the print queue?
Yes. Requesters can see their own jobs and current status, including work that is waiting on requirements, queued, printing, complete, failed, or cancelled. They don't need access to the operator view to check what happened.
Can the queue prioritise urgent jobs?
Yes. Rules can assign queue priority, and operators with the right permission can prioritize or deprioritize a queued job. This lets a team define its normal order while still handling a real deadline or production issue.
What happens when a print fails?
The failed outcome is recorded on the job with its printer and event history. Email notifications can inform the requester, and a reprint can be created from the existing job without uploading and configuring it again. Failure data is also available in analytics.
Do I need a queue system if I only have a few printers?
There isn't a useful printer-count cutoff. Look at the coordination work: files arriving in several places, repeated status questions, jobs needing to be reassigned when a printer goes down, or no reliable history after a failure. A shared queue helps when those tasks are taking meaningful operator time.
Related
- 3D printer fleet managementThe machines the queue dispatches to: state, routing, maintenance, and utilization.
- 3D print queue management guideThe long-form version: disciplines, exceptions, intake gating, and what to measure.
- Print queue, definedA short, self-contained definition plus how shared and per-machine queues differ.
See your current queue in one place.
Tell us how work arrives and how operators decide what runs next. We'll use that process in the demo.
hello@pluraprint.com · No commitment required