We are speaking of the time it takes for the workflow state machine to notice that task A is complete, thus satisfying a wait condition in a workflow definition, which then creates task B. User1 marks task A complete, & it takes between 2 & 20 minutes for task B to be created. Here is what I’ve learned:
The most common solution found on the forums is to cleanup the AsyncOperationBase table. It is said that performance will suffer if this table contains > 1 million rows, however, ours only contains 22K.
With CRM 2013, MS created a new type of workflow called “real time workflows”. These are the ones without the check next to “Run this workflow in the background”. We cannot use those because real time workflows cannot have wait conditions. In CRM 2011, it was usually just a few seconds before the state machine noticed a task complete & created the next one. It seems that with the introduction of real time, the other types are even further “in the background” … the most pertinent statement to this effect is from the URL below: “Background workflows are generally recommended because they allow the system to apply them as resources on the server are available. This helps smooth out the work the server has to do and help maintain the best performance for everyone using the system. The drawback is that actions defined by background workflows are not immediate. You can’t predict when they will be applied, but generally it will take a few minutes.”
Is there any possible solution using which the workflow process will help create task B in lesser time?