locked
Preventing state machine workflow instance from suspended in Windows Workflow Foundation 4.5 RRS feed

  • Question

  • I am using both wcf service and workflow in a mvc project. The issue is I need to have some kind of control on the transitions so that the instances won't get suspended. If some exceptions happened due to server going down or wrong parameters,  either the transition succeeds and the instance moves to the next state,  or instance stays at the current state and make no change. 

    Any suggestion will be greatly appreciated.


    Friday, December 20, 2013 9:26 PM

Answers

  • Hi,

    You can refer the second link which contains a blog:


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. <br/> Click <a href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.

    • Marked as answer by Norb Tuzki Monday, January 6, 2014 2:36 PM
    Monday, December 30, 2013 9:09 AM

All replies

  • Hi,

    I think you can try creating a Custom Exception Handler to replace suspendActivity. For more informaion, you can refer here

    #Handling Workflow Exceptions

    http://docs.oracle.com/cd/E13214_01/wli/docs70/studio/ch9.htm#1229929

    http://stackoverflow.com/questions/1833091/suspending-the-workflow-instance-in-the-fault-handler

    Hope it can help you.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. <br/> Click <a href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.

    Monday, December 23, 2013 7:31 AM
  • Thanks for the reply. However, the first link is the documentation of workflow under WebLogic Integration Studio which is different from my framework. 

    I am working on state machine under Windows Workflow Foundation in .NET 4.5. This issue really bothers me because I need to find a way to deal with the suspension issue caused especially by server going down.

    Any help will be greatly appreiciated.

    Thursday, December 26, 2013 7:19 PM
  • Hi,

    You can refer the second link which contains a blog:


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. <br/> Click <a href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.

    • Marked as answer by Norb Tuzki Monday, January 6, 2014 2:36 PM
    Monday, December 30, 2013 9:09 AM
  • Thank you for the reply. This link helps and I get a better understanding on how to handle faults.
    Monday, January 6, 2014 2:37 PM
  • I am a bit confused. The link provided is for workflows developed using the .Net 3.0 version of Windows Workflow Foundation. But the original question indicated that .Net 4.5 was being used.

    If you are targeting .Net 4.5 workflow state machines, I believe you are going to need to use TryCatch activities.

    Monday, January 6, 2014 6:10 PM