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

Question

Question

Workflow taking too long to run

Workflow
Updated August 27, 2014
asked on August 27, 2014

Hi everyone,

 

I dont know way, our workflows are taking a long time to run, they are running ok, but sometimes one workflow takes like 20 minutes to indetify a change and move a document!, Does anyone knows how to troubleshoot this or have any advice or documetation to see this performance issue?

 

thanks for the help

 

0 0

Answer

SELECTED ANSWER
replied on August 27, 2014

Look in the Workflow Admin Console under Monitoring. Pick the Subscriber and open the Subscriber Trace. On the repository tab, you can see if there is a backlog of notifications to be processed.

2 0

Replies

replied on August 27, 2014

The first things I would look at are CPU and memory usage. Is the server maxing out? How many workflows are currently be used? Is it on a dedicated server or are other applications installed on the same server?

0 0
View 1 previous reply
replied on August 27, 2014

Hi ,

So, CPU and memory are good around 12% and memory around 5 GB of 32 GB!, the Wokflow sever is alone on the server, and we have around 21 a 22 workflows working!

0 0
replied on August 27, 2014

Have you confirmed that it isn't a matter of the document entry lock not being released? It may be the workflow is waiting for a lock to be released before evaluating that change. 

 

I think the key to solving this is identifying the reason for this to happen "sometimes". Maybe it's a particular users machine not communicating to the server in a timely manner, maybe people are not releasing the entry lock. Maybe something causes a wait to occur in the workflow that causes it to stop what it's doing until a certain amount of time has elapsed. 

 

I would check the event viewer and workflow administration console for any potential errors happening that also could be the root of the problem.

0 0
SELECTED ANSWER
replied on August 27, 2014

Look in the Workflow Admin Console under Monitoring. Pick the Subscriber and open the Subscriber Trace. On the repository tab, you can see if there is a backlog of notifications to be processed.

2 0
replied on August 27, 2014

Hi everyone,

 

So thanks for the advice!, I went to Workflow Admin Console under Monitoring, and find out that we had an entry which was having the error of entry lock, after trying to stop them, and disable the workflow, but still having the same problem, purhaps because it had some persisted instances. And also we found out that some workflows were not been started, but if we tested them through workflow would work fine!

But we didnt have much time to troubleshoot , so we decided to create another database and imported the workflows again and now is working fine.

 

Thans again for the help

 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...