Job printed but remains in the queue  

RE: Job printed but remains in the queue

I am having the same issue.  Though I am not sure it is not doubling the job the moment I click the "set ready" button.  I suspect this because when I look at the print queue timeline on the "print queue" tab it already shows a repeat of the same job projected to print as soon as the first one is done.  It doesn't do this for the other jobs on the schedule, but once a new job gets to the top of the list and "set ready" is clicked, it starts printing the job and adds an additional to the timeline.  I guess that's the same as your problem, just stated in a different way.  

For me, it started after the latest FW update.  Perhaps it is because the jobs have new names "Print job ###", and doesn't delete the original name matched from the queue or something.   But, of course, that's just a guess without the code to see.  

Regardless, I second the issue.

PrusaLink type (Raspberry Pi Zero / Pi 3 / Pi 4) - Prusa MK4 with WiFi built in

PrusaLink version - ?

Printer type - MK4

Printer UUID (you can find it in Printer detail page - address line) - bffc15cc-83e5-4eb5-8b63-696d6c8e37bb

Printer firmware version - MK4_MK3.9_firmware_6.0.0.bbf

PrusaSlicer version (if applicable) - PrusaSlicer-2.7.4

Description of the bug, including steps to reproduce (if possible). - As described.

RE: Job printed but remains in the queue

I submitted this bug a while back.  It just happened to me again tonight, it added the previous print to the queue all by itself after I started a newly uploaded print manually at the printer.  I have never used the queue and I was paying close attention, checking the queue every time I uploaded a file to see if it erroneously added it to the queue (I only ever selected "upload file").

RE:

This happens almost every time for me. I slice, click 'Send to connect', select the (single) printer that I have, and see 'Add to 2. position in the queue'.

When I look at the print queue the previous, successful, print is still in the queue. Setting the machine ready consumes that same job again.

Print queue is useless for me because of this. I find this incredibly annoying.

I hope this is related to alpha firmware 6.2.0-alpha2, and it will be fixed in the next stable (whenever that is, its concerning there have been no further updates in almost 3 months now)

RE: Job printed but remains in the queue

Actually it never happened again to me since then

RE: Job printed but remains in the queue

Also experiencing this about 50% of the time... can't rely on the queue since it's never correct, unless I manually delete things from it.

RE: Job printed but remains in the queue

Coincidentally, this has been much more reliable since I replied a month ago, it makes slicing multiple plates and adding them to the queue actually functional now, which is nice

RE: Job printed but remains in the queue

I experience this every time. 

My workflow: slice, send to Connect, select my one printer, Add to print queue or Skip Queue

Every time a print completes, it remains in the queue. 

RE: Job printed but remains in the queue

I was mistaken in my jubilation earlier. This is still an issue for me also.

I slice, send to connect (queue is empty, print now), it finishes, and while the printer is on the '100% print finished screen' the job is still in the queue, with the message 'The printing time of the last job is unknown, the following jobs will not be displayed', even though the timeline indicates the job has finished.

If I set the machine as ready it prints it again, which is obviously rubbish.

Is there some network wobble that is stopping the printer from telling Connect it's finished? I'm using Eth so it's not a WiFi glitch.

RE: Job printed but remains in the queue

After starting a job and leaving it for a some unknown time, checking back in Connect and I can see that the same item is in the print queue again. So it seems that its not the printer that isn't indicating the print is done, somehow Connect is just adding it to the queue twice. This should be easy to spot, where is Prusa support?

RE: Job printed but remains in the queue

Same issue here with FW 6.2 and before.

RE: Job printed but remains in the queue

Same problem. Prints stay in the Print queue (who needs it?) after they are finished. Please let us switch off the print queue, most of us dont need it.

RE: Job printed but remains in the queue

At the risk of premature celebration as happened to @Flynny75, the queue has been working for me lately.  I have upgraded from MK4 to MK4S, and have updated firmware and Prusaslicer whenever those come out, for context.

I hope it stays reliable, but it has worked and then not worked again before.

RE: Job printed but remains in the queue

I run a print lab with a MK4 and Prusa XL (5T), and this seems to be a consistent issue with the Prusa XL, but not the MK4. 

I have to tell my users to be mindful of jobs in the print queue, to ensure filament is not wasted on redundant prints.

Is there any indication that the issue has been acknowledged by Prusa or if a fix is in the works?

RE:

This is still an issue. I'm getting really tired of the printer starting to print the thing that it just finished printing. I'm seeing it happen when I add to queue from Slicer then press start on the printer's LCD. 

Related: https://forum.prusa3d.com/forum/bugs-errors/connect-is-printing-queue-items-multiple-times/

Possibly related: https://forum.prusa3d.com/forum/bugs-errors/print-starts-when-i-hit-set-ready-even-though-i-never-put-anything-in-the-queue/

RE: Job printed but remains in the queue

I have the same issue, and it makes the print queue feature useless for me. :/

RE: Job printed but remains in the queue

When using Prusa Connect directly with an MK4S, completed print jobs remain in the print queue instead of being cleared automatically. This causes confusion and may lead to unintended reprints if the “Set Ready” button is pressed, since the previous job is still queued.

Steps to Reproduce
-Upload a print job to the printer via Prusa Connect.
-Start the print (“Print Now” or via queue).
-Wait until the print completes successfully.
-Check the printer queue in Prusa Connect.

Expected Behavior
Once a print finishes, the job should be marked as completed and removed from the active queue. Queue should be empty unless more jobs were manually added.

Actual Behavior
Finished job remains in the queue. If the printer is set to “Ready”, the same job may reprint automatically. Manual queue clearing is required after every print.

Impact
Risk of duplicate prints if users click “Set Ready” too quickly. Increased confusion for operators managing multiple jobs. Breaks expected queue workflow (automatic progression / cleanup).

Workarounds
- Manually clear queue after every job.
- Use “Print Now” instead of queuing jobs (avoids stuck entries).

System Info
- Printer: Original Prusa MK4S
- Firmware: 6.2.4+8909
- Connection: Prusa Connect via Prusa Slicer (direct, not via PrusaLink)
- Operating System: Windows 10