Articles on: Troubleshooting

Why is my print stuck starting, or marked "already done"? The 5-minute send cooldown

Why is my print stuck starting, or marked "already done"? The 5-minute send cooldown


A queue item won't start, and something looks off: AutoPrint shows it as the next item but sitting on a cooldown, or you try to start it by hand and get a confusing message - that it's "fully assigned to pending print jobs" and retryable in 5 minutes, or even that it's "already done" when it clearly hasn't finished. This is a safety mechanism doing its job. This article explains what it is, when it is normal, and what to do when a printer is genuinely stuck.


The safety mechanism: why we wait 5 minutes

When SimplyPrint sends a file to a printer, it treats that file as sent and will not try to send the same file again - to that printer or any other - for 5 minutes. This gives the printer time to actually download the file and begin the print. Files can be large, and a printer or network can be slow, so "started" is not instant.


Without this pause, a slow download would look like a failure. SimplyPrint would assume the printer never got the file, send it to another printer, and you would get the same part printing on two machines. The 5-minute cooldown is what stops that. It is deliberate, and most of the time it clears on its own within a minute or two, the moment the printer confirms the print has started.


What it looks like

You will run into the cooldown in two places:


  • With AutoPrint. The AutoPrint widget shows the item as the next to print, but with a cooldown instead of starting. The reason reads "Printer has already attempted to start a print within the last 5 minutes", and the status explains "we try once every 5 minutes, to not risk sending the same file to your printer twice".
  • Starting a print by hand from the queue. When the item's copies have been sent and are waiting to start, you get "Queue item is currently fully assigned to pending print jobs, if the print jobs failed to start the queue item will be retryable 5 minutes from the previous start" - that one is the cooldown. If every copy has already been started, you instead get "Queue item is already done, it has already been started on all assigned prints, either completed or in progress".


These two messages are easy to misread. The "fully assigned to pending print jobs... retryable 5 minutes" message is the cooldown in action: the file has been sent and SimplyPrint is giving it time to start, so if the send is stuck the item waits here until it can retry. The "already done" message is different - it means every copy of the item has already been started (a copy may still be printing right now), so there is nothing left to send. Neither message means the item has necessarily finished.


This happens even without AutoPrint

The cooldown is not an AutoPrint feature - it protects every way a print gets started. Whether AutoPrint started it, 1-Click Print started it, or you clicked start on a queue item yourself, once a file has been sent to a printer that item is held for 5 minutes before it can be sent again. So a manual queue start can absolutely refuse to start with the "fully assigned to pending print jobs" message (or "already done"), for the same reason.


When the printer is genuinely stuck

Normally the cooldown clears itself. But if an item keeps cycling - attempting to start, cooling down, attempting again - the printer probably cannot actually receive or start the file. It is stuck part-way through, so SimplyPrint keeps waiting for a start that never comes. Common causes:


  • The printer's SD card or storage is full, so the file cannot download.
  • A network issue between SimplyPrint, your host, and the printer.
  • A firmware issue on the printer.
  • A lock or stuck state in the SimplyPrint Client (or whatever host or agent you connect through).


How to unstick it

  • Check the printer's SD card / storage and clear space if it is full.
  • Check the network and the printer's connection.
  • Check the printer's firmware is up to date and the printer is responsive.
  • Check the SimplyPrint Client (or your host / agent) for a lock or a stuck upload, and restart it if needed.
  • Power-cycle the printer - turn it off for a couple of minutes. Once the printer is out of its stuck "receiving" state, that job is released and SimplyPrint can send the file to another printer instead.


If an item keeps getting stuck on the cooldown after you have checked the SD card, network, firmware and client, contact us at contact@simplyprint.io - a repeatedly stuck send usually points to a printer or host issue we can help pin down.


Updated on: 04/07/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!