Articles on: SimplyPrint features

Why won't my printer print this queue item? Using the queue inspector

Why won't my printer print this queue item? Using the queue inspector


A queue item is sitting there, a printer is free, and nothing happens. Almost always this means the item and the printer don't match on something - the wrong filament, the wrong nozzle, or a group rule that's keeping them apart. SimplyPrint can tell you exactly which one. This guide shows you how to open the printer-compatibility view (the Queue Inspector), read the reason, and fix the one thing that's blocking the print.


The print queue and the Queue Inspector are part of the Pro plan and up. See pricing for the full plan comparison.


This is the most common queue question we get, so it's worth understanding how matching works once. If you're new to the queue, start with the print queue overview and come back here when something won't start.


In this article


How printer matching works

Before a printer can start a queue item, the two have to agree on every requirement at once. The item carries a set of needs - a filament/material tag, maybe a nozzle size or nozzle type, maybe a bed type, a model size/fit, temperatures, custom tags, the file type its firmware can run, and any printer/model/group restrictions you set on it. The printer has its own configuration - what's loaded, what nozzle and bed it has, what firmware it runs, and which groups it belongs to. A match happens only when the printer satisfies all of the item's requirements. Miss one, and the printer is skipped.


That's why a free printer can sit idle next to a full queue: it isn't "broken", it just doesn't match any of the items right now. The inspector turns that invisible decision into a plain-English list of which printers can run the item and, for the ones that can't, exactly why not.


The inspector reports raw compatibility only. It tells you whether a printer is technically capable of running the item - material/colour, nozzle, bed, size/fit, temperatures, custom tags, firmware file support, and your printer/model/group restrictions. It does not report queue-status states (a paused or back-burner item) and it does not list printers that have been pulled out of the matching pool (a printer in maintenance or out of order, or one whose bed isn't cleared). Those are covered separately near the end of this article.


Open the queue inspector

You can reach the same printer-compatibility view from two directions.


From a queue item:

  1. Open the item's big item view (click the item in the queue).
  2. Find the Printer compatibility section (its tooltip reads "See which printers match this item").
  3. You'll see which printers can run this item, and for each printer that can't, the reason it was excluded.
  4. For the whole picture, use the Open full inspector link to open the Queue Inspector modal.


From the printers page you can look at it the other way around - pick a printer and see which queue items it's able to run. Both views read the same matching rules, so they always agree; use whichever direction matches the question you're asking ("why won't this item print?" vs "why is this printer idle?").


Read the reason first, then change one thing. Most stuck items are blocked by a single mismatch, so there's usually exactly one fix - no need to change five settings at once.


The rest of this article walks through every reason a free printer might not start an item: first the compatibility reasons the inspector reports, then the queue-status and matching-pool cases it deliberately leaves out.


Compatibility reason: wrong filament or material

This is the most common one. The item is tagged for a filament or material (say PLA, or a specific brand and colour) and the printer has something else loaded, or nothing recognised at all. The printer won't print PETG parts in PLA just because it's free.


What to change:

  • Load the right filament into the printer, or
  • Update what SimplyPrint thinks is loaded (assign the correct spool to the printer), or
  • If the item's tag is wrong, edit the item's filament/material tag so it matches what you actually want to run.


Filament and nozzle tags come from your tagging setup. If items aren't getting the right tags automatically, see auto-tagging and auto printer-model selection.


Compatibility reason: wrong nozzle size

The item needs a particular nozzle size (for example 0.4mm) and the printer is set to a different one (0.6mm, 0.2mm), or it needs a particular nozzle type or volume the printer doesn't have. Nozzle setup affects the sliced result, so SimplyPrint treats it as a hard requirement rather than guessing.


What to change:

  • Swap the printer to the nozzle the item needs and update the nozzle on the printer in SimplyPrint, or
  • If the item's nozzle tag is wrong, correct it on the item.


Compatibility reason: wrong bed type

The item is tagged for a specific bed/build plate (for example a textured PEI plate) and the printer has a different plate fitted. This matters when a print's adhesion or finish depends on the surface.


What to change:

  • Fit the bed the item expects and set the matching bed on the printer, or
  • Relax the item's bed requirement if any plate will do.


Compatibility reason: the printer's firmware can't run this file

The inspector also checks whether the printer's firmware can actually run the item's file. A printer whose firmware doesn't support that file type is excluded, because pushing it would just fail at the machine. This is a hardware/firmware capability check on the printer, not a group rule.


What to change:

  • Send the item to a printer whose firmware supports the file, or
  • Re-slice or re-add the item in a format the target printer can run.


This is different from a group's accepted-file-types setting, which is an add/move-time membership restriction (it controls what you can put into the group, not what the inspector reports). For that setting, see queue groups.


Compatibility reason: the item's own printer, model or group assignment excludes it

Every queue item can carry its own restrictions: allowed printers, allowed printer models, or allowed groups. If you (or an integration) pinned the item to specific printers or models, every other printer is excluded by design - even a perfectly capable one.


What to change:

  • Open the item and check its allowed printers/models/groups.
  • Widen the selection (or clear it) so the printer you want is included.
  • If the restriction is intentional, this is working as designed - load up one of the printers it's actually allowed to run on.


Compatibility reason: the queue group excludes the printer

This is the one that trips people up most, so read it carefully. A queue group has a for printers / models / groups setting. That setting controls which printers the items in that group are allowed to MATCH and print on. If the group is set "for" a certain set of printers and your free printer isn't in that set, items in the group will never run on it.


Important: choosing "for printers / models / groups" on a group only controls matching. It does NOT move items for those printers into the group, and it does NOT pull printers into the group. Items only enter a group when you add or move them there. So a printer can be perfectly capable and still be excluded purely because the item's group isn't pointed at it.


What to change:

  • Open the group editor and check its "for printers / models / groups" selection.
  • Add the printer (or its model/group) to the group's allowed set, or
  • Move the item into a group that's pointed at the printer you want to use.


This matching-not-moving behaviour is explained in full in queue groups. If items seem to "not move" to where you expect, that article is the one to read.


Compatibility reason: it's a virtual group item

If the item lives in a virtual queue group, it is never sent to a real printer by design. Virtual groups are for tracking work you're not actually starting through SimplyPrint (outsourced or off-platform jobs), so there's nothing to match - you advance these by hand with +1 finished and Mark finished.


What to change:

  • Nothing, if you meant it to be virtual - mark progress manually.
  • If it should print on a real printer, move the item out of the virtual group into a normal one. See queue groups.


Not a compatibility issue: the printer is out of the matching pool

Some printers won't take new work even though they'd be a perfect compatibility match. These printers are removed from the matching pool before compatibility is ever checked, so they don't show up in the inspector's reason list at all - you spot them from the printer's own status and from the queue counts, not from the inspector. Two cases do this:


  • Maintenance or out of order. A printer marked as in maintenance or out of order is taken out of the matching pool on purpose, so the queue won't hand it new work. Automatic starting (1-Click Print and AutoPrint) skips these printers too. You can see the state on the printer itself. See printer maintenance for how maintenance status works.
  • The bed isn't cleared. If you have printer beds must be cleared turned on (a 1-Click Print setting), a printer whose bed still holds the last print won't be offered a new item until the bed is marked clear. This is a safety setting so you don't start a print on top of a finished one. The queue page has an Awaiting bed clear count that jumps straight to the printers waiting on a clear.


What to change:

  • Finish or cancel the maintenance, or take the printer out of its out-of-order state, and it rejoins the pool.
  • Clear the bed physically, then mark it cleared in SimplyPrint, and the printer becomes eligible again.
  • If you don't want the bed gate, you can turn off "printer beds must be cleared" in queue settings - but most farms keep it on for a reason.


Not a compatibility issue: the item is paused or on the back burner

These are queue-status states on the item, not compatibility problems, so the inspector ignores them - it inspects raw compatibility regardless of whether the item is currently eligible to start. A paused item stays in the queue but won't be picked up until you resume it. A back-burner item lives in a separate low-priority lane; depending on your settings, automatic matching may skip it. Specifically, the exclude back-burner items from automatic matching setting means 1-Click Print and AutoPrint leave back-burner items alone (you can still start them manually).


What to change:

  • Resume a paused item to put it back in play.
  • Move a back-burner item to the normal queue, or start it manually, or turn off the back-burner exclusion in scheduling and distribution if you want automation to consider it.


Let the to-do list do the work

Reading the inspector item by item is great for one stuck job. When you want the whole farm sorted, use the to-do list. Every time you open it, SimplyPrint reads your entire queue and works out the single highest-impact physical change that would unlock the most prints right now - then hands it to you as a checklist.


The to-do list is part of the Print Farm plan and up. The inspector itself is available from Pro.


So instead of opening ten items and discovering ten "wrong filament" reasons, the to-do list tells you "put PLA in this printer and it can print 16 items", grouped by queue group, with one-click actions to set the tag, assign a spool, or jump to the printer. It's the same matching logic the inspector uses, turned into a prioritised worklist. The two work together: the inspector answers "why won't THIS item print?", the to-do list answers "what should I physically change next to unblock the most prints?".


If a printer keeps ending up idle, it's also worth checking how the queue is set to distribute and order work - see scheduling and distribution. Settings like "never skip queue items" change whether a printer waits for the right filament or moves on to something it can print.



Updated on: 24/06/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!