Allow restarting failed documents from the dashboard #580
Replies: 2 comments 4 replies
-
Hello!
Apart from the issue you've mentioned, I can't think of any errors that only occur once in a while. Pretty much all issues during the consumption process are permanent, and retrying won't fix that. So, rather than trying to work around your problem, I'd like to try to address the "locking" issue you're facing. When polling is used, paperless regularly checks a newly detected file until it has not changed for a set amount of time (default: 1 second). I believe that this is not high enough in your case, maybe due to some sort of networking / file system caching. I'd like to prepare a patch and see if that fixes your issue. Would you be willing to test with that patch? If that fixes your problems, I'll get the change rolled into the next release.
Deployment is much easier when everything is in one container. In theory, it's possible to restart just the consumer without restarting the entire container, but I need to put some configuration in place so that the cli tool for that actually works. |
Beta Was this translation helpful? Give feedback.
-
Will do. And thanks again, that was a pretty quick turnaround time for that issue! 😊
|
Beta Was this translation helpful? Give feedback.
-
Hi there,
with version 1.1 we got the progress of the consumption process shown on the dashboard. There, it also shows failed documents. But currently, this is only informational and there is no way to restart the consumption process for a failed document. I think it would be useful to have a restart button for failed documents.
(One could also argue that paperless-ng could just retry by itself but IMHO just retrying isn't always the answer, so I giving the user the possibility is the more sensible option.)
Background: My setup is centered around my NAS which has a SMB share to which my scanner directly saves scanned documents. The share is also exported via NFS and mounted to paperless-ng as the consumption directory. As NFS doesn't support inotify, I set paperless-ng to poll the consumption dir. From time to time, consumption of a document fails for what I suppose is a locking problem (i.e. the file isn't fully being written yet but paperless-ng already tries to read it). When this happens, I have to restart the whole container so the consumer process picks up the document again, this time it will finish successfully.
Due to that, I would also appreciate if the webserver and the consumer would be separate containers, as in the original paperless - but having a retry button in the UI might be a simpler solution?
Cheers and big thank you for building this!
Beta Was this translation helpful? Give feedback.
All reactions