How can we improve the DocuWare Desktop Apps?

Import jobs keep going or autorestart after failure

Whenever an import job fails for whatever reason, that job stops importing altogether and you have to manually go in there and restart the failed job. This is not ideal as I am not always able to connect with the customer right away to restart the jobs, so there might be a time period where users are not getting any documents imported. It would be great if the import job didn't stop when it failed and maybe somehow could send an email notification to the admin but still kept going. Or autorestart after a certain period, whatever makes the most sense. But having to manually restart them makes it more difficult for all parties.

12 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Gregory Roundfield shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Ryan Holloman commented  ·   ·  Flag as inappropriate

        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.

      • Karin May commented  ·   ·  Flag as inappropriate

        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.

      • AdminDocuWare Product Management (Admin, DocuWare) commented  ·   ·  Flag as inappropriate

        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

      Feedback and Knowledge Base