Question

Workflow does not work

Updated May 12, 2017

asked on April 25, 2017

Hi Everyone,

I have been working with Laserfiche for a few years now and I really like the product. However, I am experiencing an issue now and I'm in need of some help. I modified a template and created a workflow to allow for more efficient filing of some documents. However, the documents now do not move to their new location after the template is applied. When I run the test in the workflow designer, I get this error:

"This request operation sent to net.tcp://laserfiche:8085/ManagementService did not receive a reply within the configured timeout (00:00:30). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client."

I also realized that some of my other workflows don't work now also. Any assistance or advise provided on this matter is greatly appreciated.

Cheers,

Heatha

0 0

Replies

replied on April 25, 2017

Are some workflows still working?

What's the difference between the workflows that are broken and the ones that work?

Are there any LFWorkflow errors in the applications and services logs?

0 0

replied on May 12, 2017

Hi Erik,

Thank you for responding to my inquiry. I was able to resolve the issue slightly by putting some conditions in the workflow but now some of the entries are not being renamed accurately. For example the workflow specifies that an entry is renamed using the date of the document and the subject of that document, however some entries are being renamed with only the date appearing as the entry's name. A few of the entries do not move at all but are renamed and only the date appears. When I run a test on the entries that don't move, I receive this error message:

This request operation sent to net.tcp://laserfiche:8085/ManagementService did not receive a reply within the configured timeout (00:00:30). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

0 0

replied on May 12, 2017

Did the ones that didn't get renamed correctly have values in the "subject" field when the workflow ran?

The timeout error is usually an indicator of high load on the SQL. It could be that SQL is underpowered for all the activity or it could be that you have a runaway workflow that is causing a lot of activities. You can try the statistics report () instead of a full search to get an idea of how busy your Workflow server is.

0 0

You are not allowed to follow up in this post.

Question

Question

Workflow does not work

Replies

Sign in to reply to this post.