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

Question

Question

We have to restart the Laserfiche Workflow Subscriber 9.1 service in order to get a condition starting rule to fire.

asked on August 15, 2014

 

The Starting rule is on an entry created in a specific folder, and creates shortcuts in another folder to enable TRM use.  Whenever we notice that it is not firing, I restart the service, and everything triggers properly upon restart.  The entries are being created by a quickfields session.  We also have scheduled starting rules which do work without the restart.

 

Is there a known resolution to this?  I shouldn't have to repeatedly restart a service in order to get the condition to fire.

0 0

Answer

SELECTED ANSWER
replied on August 22, 2014

Hi Lynn, 

 

If your question has been answered, please let us know by clicking the "This answered my question" button on the response.

 

If you still need assistance with this matter, just update this thread. Thanks!

0 0

Replies

replied on August 15, 2014

What version of Workflow are you using? Are there any errors in the subscriber log in the Workflow Administration Console?

0 0
replied on August 15, 2014

Version 9.1.1.365.  These errors show up in the Subscriber_error.log: 

 

8/14 at 2:17 pm - the session has been reset by the server: "An exception of type 'Laserfiche.Workflow.WorkflowConnectionResetException' occurred and was caught."

 

8/15 at 7:51 am: An exception of type 'System.IO.FileNotFoundException' occurred and was caught.

 

8/15 at 8:03 am: An exception of type 'System.Security.Cryptography.CryptographicException' occurred and was caught.

0 0
replied on August 15, 2014

We restarted the service at 10:58, and everything processed as expected.  I am waiting to see if the users scan anything else to watch if it continues to run or not.

 

0 0
replied on August 15, 2014

If it happens again, please have your reseller open a case with Tech Support and upload the error logs.

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

Sign in to reply to this post.