Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat happens to recurring workflows once the async service is restarted?
    text
    copied!<p>Our org is planning on basing parts of our business model on the premise of <a href="http://gonzaloruizcrm.blogspot.com/2011/05/quite-often-we-have-business-process.html" rel="nofollow" title="Scheduling recurring workflows in CRM">recurring workflows</a> in CRM 2011. However, we sometimes run into an issue with a backed up workflow queue, or for some reason need to restart the server (update rollups, etc.), or in some other way find we have to restart the CRM's async service.</p> <p>What would happen to any workflows in the "waiting" phase in this scenario? </p> <ul> <li>I see the workflow in the <code>AsyncOperationBase</code> table with the "waiting" <code>statuscode</code>; when the service comes back online, does it look at this table and resume accordingly?</li> <li>In the above scenario, what what would happen if the service was stopped, and in the interim, the workflow reached its <code>PostponeUntil</code> date? Does the service look at all non-complete future <em>and</em> backdated workflows and decide what to with each? Or does the workflow just fail altogether?</li> </ul> <p>Any fails in the process would obviously be a deal breaker for this element of the CRM system, and we'd have to develop an external component to handle recurring items.</p> <p>I'd <em>expect</em> there to be some documentation on this, but I can only guess that the <a href="http://msdn.microsoft.com/en-us/library/microsoft.xrm.sdk.workflow.waitsubscription.aspx" rel="nofollow" title="WaitSubscription Class"><code>WaitSubscription</code></a> class has something to do with this topic, but it's for the most part undocumented.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload