I want to get back to this quite old (but still existing) problem.

We have a shared folder on our docuware server which gets imported automatically via the desktop apps. The files inside are created by another individual software. Sometimes it happens that the dwcontrol-files contains an invalid xml character or the control file referes to a config which does not exist and so on. In this case, the whole import process stops without notifying and also all other (valid) files are not imported any longer.

It would be much nicer to import everything valid and just leave the invalid files in the folder (.. and maybe send an email that something failed).

We have the same issue; client has Desktop Apps Import is installed on server; when job fails the administrator is not notified and jobs begin to build up in the folder. Customer sees this as a major issue with DocuWare (version 6.9) since they import between 1-3 thousand documents every day. If the issue goes unnoticed for for a few days, over the weekend for example, then there could be 3-9 thousand documents which all need to be processed! To our customer that is unreasonable because these documents are related to a retail process and must be available at any time, but if they are waiting to be imported, then they are irretrievable within DocuWare.

To answer on #3 from DocuWare Product Management's question:
An example of an error which may cause the import to fail is the application tries to import the file before it has finished being copied into the import folder. In our configuration we are using document identification which does not provide a way to increase the amount of time import waits before attempting.

Furthermore, couldn't the import module simple move the failed document to a triage folder so that it can continue processing other documents? This would provide a way to handle the problem which caused document to fail but could allow the import to continue working on other documents without causing a huge back-up of pending documents.

I have the same problem. We have one server where documents are dropped after scanning. I have an import job set up to import when the documents appear in a specific folder on the scanner. About once per 8-10 days, the import job stops with a "Connection to the server is not possible" error and does not restart on its own.

Docuware version 6.6.2790.6178.

To add to the idea above, it would be great if the import job would continue to check for server connection on intervals of a configurable amount of time instead of stopping completely.

Hello Mr. Roundfield,

Thank you for your Feedback, I have some questions, however, to understand more about the process where this happens.

1. can you specifiy which version you are using. Recently we have changed some background processes, so job should only really fail rarely (Which means the administrator has to "fix" something). There is also an automatic retry for jobs that fail(that only runs once)

2. Why are you restarting the jobs for the customer. Can he restart the jobs himself? Or is this something he won't do.

3. what do you mean with "It would be great if the import job didn't stop when it failed [...] but still kept going". If a job fails, there is a reason why it can not go on.
Very often changes are needed to fix a problem and it only makes sense to restart the job afterwards. Can you give some examples of failed jobs on your end where this might be useful?

Thanks in advance
DocuWare Product
Christian Prantl