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

Question

Question

Workflow Stopped Working

asked on October 30, 2014

I have a workflow which has just suddenly stopped working as designed.

Normally, the workflow was automatically started when a document is dropped in a particular folder in the Laserfiche Repository. While troubleshooting I discovered that the workflow works if I manually run it from the designer after placing a document in the LF Repository folder.

All the Laserfiche associated local services on my desktop are set to automatic apart from Laserfiche VSS Writer. Can somebody help me please.

0 0

Replies

replied on October 30, 2014

Have you checked the Application event log on the Workflow Server machine?

0 0
replied on October 30, 2014

Also, since the workflow works OK when run manually, that suggests you need to look carefully at the starting rule conditions.  It helps to log in with the same account your workflow connection uses. That way, if something like template or document security has changed for that user, it will be easier to see. 

0 0
replied on October 31, 2014

If the above suggestions don't lead to a solution, please also verify that the repository in question is properly configured under the Monitored Repositories section of the Workflow Configuration Manager.

0 0
replied on September 9, 2015

Hi

I got the same case with a client right now. Suddenly all the workflows now don't work by rule. If i manually trigger the workflow works fine. These are not new workflows, they all use to work fine. Now if i create a simple new one doesn´t work, but only by rule.

I cant find errors on the logs of the event viewer.

 

Did you get the answer to this?

 

I already:

Re-configure the server

Re-Start services

Re-create the profile

Enter to the repository with the workflow user and all looks fine.

 

0 0
replied on September 9, 2015

Check the Workflow Subscriber Trace to and see if the repository events are being evaluated correctly. If you don't see any events coming in, then you may want to reconfigure the Workflow Subscriber and also try removing and adding back the monitored repository.

0 0
replied on September 21, 2015 Show version history

I got 3 different cases for this issue with this client.

 

At the end we solve it with the help of LF support.

 

The top line issue is WF and SQL in the same server and a lots of persisted instances. You cannot believe how many of them and it was not a out of control WF, they actually got toooo many instances alive.

 

 

Also at the same time another client got the same issue but in this case was that for some reason WF from time to time cant see the server by name, so we change all the connections by IP and that solve the case.

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

Sign in to reply to this post.