You are viewing limited content. For full access, please sign in.

Question

Question

Movepage periodically fails to delete original

asked on October 30, 2014

We have been having a periodic issue with the movepage command. Images scanned in QF and then stored in a "Incoming Documents" folder. Workflow executes, performs validation and renames/moves the document via the movepage command to the "Ready to Verify" folder. Everything is fine at this point. At a later time, the verifier verifies the document, changes a metadata field to "Verified"  and saves it. Workflow then executes the movepage command and successfully moves/renames the document to the final "Member Documents" folder. Here is the problem, periodically, for some unknown reason, the document is in the "Member Document" folder with the images, however, the document name still exists in the "Ready to Verify" folder with "no pages" and the timestamp on both documents is exactly the same. I would assume a locking conflict but there is nothing in the SQL, WF or Laserfiche logs. We are on version 9.1.1 Service Pack 1 (9.1.1.548). We had the same sporadic problem in earlier releases also. Any suggestions on how to better debug this issue? This WF processes hundreds of the same type of document each day successfully.  We may end up with none on a given day or dozens.

0 0

Answer

APPROVED ANSWER
replied on October 31, 2014

Please contact your Laserfiche reseller to open a support case. We'll need to review your workflow at least, and also collect the Workflow logs and event logs to have as background information at least.

0 0

Replies

replied on October 30, 2014

Did you check the workflow instance details for those documents? Are there any errors listed?

0 0
replied on October 31, 2014

Miruna, yes. No errors.

0 0
APPROVED ANSWER
replied on October 31, 2014

Please contact your Laserfiche reseller to open a support case. We'll need to review your workflow at least, and also collect the Workflow logs and event logs to have as background information at least.

0 0
replied on November 3, 2014

Alexander, we had previously submitted wf and logs to support and they were unable to determine the cause. I am checking to see if others have experienced a similar issue. Thanks!

0 0
replied on November 3, 2014

We'll follow up with your reseller and work with them on the matter.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.