locked
CRM 2011 - Wait until not working RRS feed

  • Question

  • I've upgraded from CRM 4 to CRM 2011 and when i run a workflow it hangs on wait until, even though the until condition has been satisfied.

     

    Any suggestions?

    Monday, June 6, 2011 6:36 PM

Answers

All replies

  • You have verified that the async service is running?
    Jamie Miley
    http://mileyja.blogspot.com
    Linked-In Profile
    Follow Me on Twitter!
    Monday, June 6, 2011 6:53 PM
    Moderator
  • Yeah, first thing i checked :)
    Monday, June 6, 2011 6:53 PM
  • You would think so, but I figured I would ask.  I would say that you should try to restart the service to see if that helps once.
    Jamie Miley
    http://mileyja.blogspot.com
    Linked-In Profile
    Follow Me on Twitter!
    Monday, June 6, 2011 6:55 PM
    Moderator
  • Done that, restarted all 4 services(Async, Async Maintenance, Sandbox processing and unzip)
    Monday, June 6, 2011 6:58 PM
  • Mohamed,

     

    Can you provide more details how your workflow is configured and what you are experiencing?


    Gonzalo | gonzaloruizcrm.blogspot.com


    Monday, June 6, 2011 7:00 PM
    Moderator
  • I've got a workflow which has started, and i have a step "Wait until approval status equals rejected,accepted", when the user changes the request status from pending to either one, the workflow says waiting for resources and then waiting again without continuing
    Monday, June 6, 2011 7:02 PM
  • When you open the system job form, there is a "message" section, does it have anything there? (this section is useful for diagnostics of workflow jobs).

    Some other questions

    1. Dod the workflow start before or after you upgraded?
    2. What happens if you manually resume the workflow?

    Gonzalo | gonzaloruizcrm.blogspot.com

    Monday, June 6, 2011 7:09 PM
    Moderator
  • The workflow use to work before i upgraded, and is working on another crm 2011 server

    the message section has nothing.

    when i manually resume the workflow it still stays on the same step

    Monday, June 6, 2011 7:46 PM
  • Your async server might be busy if there are multiple things it needs to be processed. If you resume, does it go to "Waiting for resources" and then to "waiting" or what is the beheavior you observe? The more details you provide then the more help you will get


    Gonzalo | gonzaloruizcrm.blogspot.com

    Monday, June 6, 2011 7:59 PM
    Moderator
  • Yes that's exactly what happens, waiting for resources then waiting again
    Monday, June 6, 2011 8:00 PM
  • There might be something corrupt with your workflow. You can try deleting and recreationg the wait step

    Gonzalo | gonzaloruizcrm.blogspot.com

    Monday, June 6, 2011 8:09 PM
    Moderator
  • Ok will try and i'll update you with whatever happens, thanks alot
    Monday, June 6, 2011 8:11 PM
  • Hi,

    I would suggest you to verify if AsyncOperationBase table has not grown very large. When the table contains millions of records, performance is slow and often workflows do not execute properly. This article explained (http://support.microsoft.com/kb/968520) this issue in detials for CRM 4.0 but if you found the table grown very large then try executing the steps.

    Also In update rollup 2 (http://support.microsoft.com/kb/2466086) worklfow wait condition related problem has been fixed "If you create a workflow that has a wait condition, the workflow is delayed incorrectly in Microsoft Dynamics CRM 2011."


    Thank You,
    Jehanzeb Javeed,
    http://worldofdynamics.blogspot.com
    Linked-In Profile |CodePlex Profile

     



    If you find this post helpful then please "Vote as Helpful" and "Mark As Answer".
    Monday, June 6, 2011 8:13 PM
  • Because you say that it goes to "waiting for resources" and then back to "waiting" it means that async service has actually taken the time to execute the workflow so it should not be related to async perf / service being busy

    Gonzalo | gonzaloruizcrm.blogspot.com

    Monday, June 6, 2011 8:15 PM
    Moderator
  • No it's actually quite small. I just tried a sample workflow with a wait and it worked just fine, so i'm starting to get the feeling that the workflow is in fact corrupt, even though i have 5 of them that do the same thing
    Monday, June 6, 2011 8:16 PM
  • I guess for some reason the workflow got corrupt when importing, i created a new one and it's working great

     

    Thanks alot everyone

    Monday, June 6, 2011 8:49 PM
  • Good news! Please mark the replies that were useful to you as answer.

    Gonzalo | gonzaloruizcrm.blogspot.com

    Tuesday, June 7, 2011 12:26 PM
    Moderator