Duplicate upload makes queue stuck
Every time I send files from PrusaSlicer to my MK4 I get "The file with this name is already present on the printer" in the Connect Dashboard.
I am sure I am not sending the file twice, but I consistently get this error.
Sad thing is that the printer cannot "see" or mitigate this problem and the following files are just not being uploaded. Whole queue gets stuck.
Prusa Slicer Version 2.9.4
RE: Duplicate upload makes queue stuck
within connect, did you look at the files that are stored in the cloud drive to see if you have a file there with the same name?
Shane (AKA FromPrusa)
RE: Duplicate upload makes queue stuck
Just checked and there is no duplicate there. A single file.
Also I am noticing there is no queue duplicate, is just that the queue item does not go away after the printer upload and tries again.
RE: Duplicate upload makes queue stuck
I also experienced that multiple times. When the PrusaConnect transfer between the cloud and printer gets stuck for some reason the queue will get stuck. I contacted support once while this happened but they were not able to help. "You have to understand that we cannot help you with PrusaConnect. We can only help you when printing from USB. We can only pass on information to the dev team." They had me print a test cube after that (which is pointless to me in that regard). After that I stopped to report PrusaConnect related issues.
I also had cases where I uploaded three files to PrusaConnect + added the job to the queue. But PrusaConnect only copied two of the files to the printer (not the first one in queue) and lost the other one for some reason. This also lead to a printer doing nothing even though stuff was in the queue.
According to support there is no way to enable any logging related to PrusaConnect so I got absolutely not way to debug any of those issues (and support will not help me). There is some PrusaConnect proxy but I did not try that yet to debug those issues. I probably experience this about twice per week (2 out of 40-50 prints).
Since this happens quite frequently to me (due to some ethernet issue on my printer which is unrelated to PrusaConnect but probably triggers a lot of races) I had the chance to test ways to unstuck the queue:
1. If you still got the file just cancel all transfers, delete the file and transfer that file again. That always works. But you need the file otherwise you are lost. This even fixes cases where a print is stuck due to a partially transferred file (as PrusaConnect streams the GCode initially). Otherwise you loose the print.
2. You can also cancel the transfer and copy the file to the USB stick. Again you still need the file.