RE: Job printed but remains in the queue
Same thing here.
- I have an empty queue.
- I slice something and send it to Prusa connect and add it to queue.
- If I look at the queue in Prusa connect there is a single job in there.
- I go to my printer and I can already see the print waiting for me on the display. I prepare the printer and click on print in the printer UI.
- Now if I go back to the Prusa connect queue there are two items in it. A duplicate of the same job, which is already printing.
RE: Job printed but remains in the queue
This is an issue for my classroom print farm of 6 printers. Often, but not always, duplicate items are printing. It is difficult to know whether a job is a duplicate or not, which is the purpose of using the queues in Prusa Connect. We usually discover a duplicate has occurred only after the complete part is delivered to a student's box and they ask why two were printed the next day.
Our workflow is exclusively:
- Slice in PrusaSlicer
- Send to Connect with the PrusaSlicer "Send to Connect" button
- Queue the job on one of the six printers
- As each job completes, clear the bed and press the "Set Ready" button on the printer screen.
We never start print jobs any other way.
RE: Job printed but remains in the queue
Googled the problem and it lead me here.
This issue has been bugging me for half a year now I think and it persists on 6.4 Firmware.
RE: Job printed but remains in the queue
Adding to this thread another report of this bug and re-capping some previous information in case Prusa devs pick this up. This bug report is now over a year old and needs fixing. I’ve emailed Prusa Support to try and get this escalated.
As already reported in this thread, duplicate jobs are incorrectly retained in the print queue, which effectively makes the print queue feature useless. Core One+, firmware 6.4.0+11974
Other related threads:
https://forum.prusa3d.com/forum/bugs-errors/connect-is-printing-queue-items-multiple-times/
RE: Job printed but remains in the queue
I am encountering the same issue as others here and I am having it happen on both my Core One+ and my MK4S+ (both on 6.4.0+11974 and using Prusa Slicer 2.9.4). I queue up a good 4 prints on each. Finish the first print on each printer. Clean and Set Ready. Walk away expecting print 2 to start on each, but it just reprints print 1 that already completed again on both machines. Also happens if I just add 1 print to queue and print it. If I go to add another print to queue it trys to put it in queue position 2 even though whats in position 1 already printed successfully.
RE: Job printed but remains in the queue
I've had this happen as well, and it seems inconsistent. I'm wondering if this is a problem on the server-side and has nothing to do with the slicer or the printer. Has anybody tried reporting it as a prusa-connect bug (assuming that's even possible)?