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

Question

Question

Work Flow Waiting/Hold Up

asked on October 19, 2015

If one work flow instance status is "Waiting" will it hold up any other work flows behind it until it is completed or if another work flow is triggered can it can run even though another workflow is running but is waiting?

 

Thanks.

0 0

Replies

replied on October 19, 2015

Every time a workflow is triggered based on the starting rules it will run a new instance of the same workflow. If the workflow is triggered and is in the waiting phase due to an activity it will not hinder the workflow from starting a new instance.

0 0
replied on October 19, 2015

Is there a limit to the number of instances that can be in progress at once? Not sure what is happening but at times it seems work flow does not work for  a period of time. In the morning everything runs great then later in the day no workflows will work (Forms, Quickfields). Everything seem like it halts then all of a sudden everything goes through later in the day.

 

Any ideas?

0 0
replied on October 19, 2015

There are limits based on the number of CPUs on the Workflow server. However, instances waiting would be saved to the database and not impact starting new ones.

Depending on the activity in your repository, it is possible that the server has a backlog of events to process. Scripts can also impact the run time of an instance. Since you're not mentioning how Forms and Quick Fields are used with Workflow, it's hard to guess what might be going wrong.

You can check the Workflow Administration Console to see whether the server has a backlog of events to process (on the repository tab in the Subscriber Trace). You can also run a statistics report to see what the load of your server is daily.

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

Sign in to reply to this post.