Answered by:
Why does a time-based CRM2011 workflow wait condition not trigger?

Question
-
Hi,
I have a CRM2011 workflow with a wait condition like the following:
Wait untip Process-Executiom Time >= [MyEntity:StartAt], then: ...
When I create a new workflow instance that meets the condition at time of creation, the wait condition will pass and the rest of the workflow will execute and terminate.
When I create a new workflow instance that does not meet the condition at time of creation, the workflow will - as expected - enter the "Waiting" state. As time passes eventually the condition will be met and I would expect the workflow to wake up and resume. But this never happens.
However, if I explicitely choose "Resume" from the Web-menu on my workflow instances, they seem to get re-evaluated: The instances which meet the condition continue execution, the others remain in waiting state.
Any idea, what's wrong here?
Thanks!
Regards,
Johannes.
Tuesday, May 24, 2011 10:20 AM
Answers
-
Hi Johannes,
You are not using "process execution time" correctly. Please refer to this article: http://blogs.msdn.com/b/crm/archive/2010/01/15/microsoft-dynamics-crm-workflow-authoring-best-practices.aspx (section 4).
Instead of using "execution time" you should insert a timeout step and give it the date when it should resume: Wait until -workflow- -timeout- -equals- {some date / duration }
Gonzalo | gonzaloruizcrm.blogspot.com
- Proposed as answer by Gonzalo Ruiz RModerator Tuesday, May 24, 2011 1:33 PM
- Marked as answer by Johannes Riemer Tuesday, May 24, 2011 2:38 PM
Tuesday, May 24, 2011 1:33 PMModerator
All replies
-
What you are imlpying in your wait condition is that the Start At is before the execution date/time. Is this what you want?
MS CRM Bing'd - http://bingsoft.wordpress.com Useful Tools CRM 4 to CRM 2011 JavaScript Converter Tool CRM 2011 OData Query Designer CRM Forum Guidance on how to Help Us Help You Tuesday, May 24, 2011 11:58 AMModerator -
Hi Johannes,
You are not using "process execution time" correctly. Please refer to this article: http://blogs.msdn.com/b/crm/archive/2010/01/15/microsoft-dynamics-crm-workflow-authoring-best-practices.aspx (section 4).
Instead of using "execution time" you should insert a timeout step and give it the date when it should resume: Wait until -workflow- -timeout- -equals- {some date / duration }
Gonzalo | gonzaloruizcrm.blogspot.com
- Proposed as answer by Gonzalo Ruiz RModerator Tuesday, May 24, 2011 1:33 PM
- Marked as answer by Johannes Riemer Tuesday, May 24, 2011 2:38 PM
Tuesday, May 24, 2011 1:33 PMModerator -
Timeout worked.
Thanks all!
Tuesday, May 24, 2011 2:38 PM