Skip to main content
B
BrianToussaint19-Tanzanite
19-Tanzanite
June 13, 2022
Solved

How to force a workflow to a specific task when stuck in limbo?

  • June 13, 2022
  • 2 replies
  • 3034 views
I am using Windchill PDMLink Release 11.1 and Datecode with CPS M020-CPS08

I have a couple of workflows that are stuck because someone chose the wrong path and now they are stuck without a routing to go. Is there a way to force route them to where they need to go?
    Best answer by HelesicPetr

    Hi @BrianToussaint 

    I know that feeling if a workflow is stuck .

    My experience is that depends on how your workflow is designed.

    If you have routes to go back in the forward path you can manually complete tasks to go where you want with correct routings by admin.

    If not then you have to start new workflow. 

     

    PetrH

     

    2 replies

    HelesicPetr
    22-Sapphire II
    HelesicPetr22-Sapphire IIAnswer
    22-Sapphire II
    June 14, 2022

    Hi @BrianToussaint 

    I know that feeling if a workflow is stuck .

    My experience is that depends on how your workflow is designed.

    If you have routes to go back in the forward path you can manually complete tasks to go where you want with correct routings by admin.

    If not then you have to start new workflow. 

     

    PetrH

     

    C
    cgautier18-Opal
    18-Opal
    July 15, 2022

    Hello BrianToussaint,

    I confirm it is unfortunately not possible to restart/resume a completed workflow activity.

    For such use-case the best way to go is to modify the workflow template to give it more flexibility and start a new workflow process.

    I wish I could help you more as I understand how important this is for you.

    KR,

    Charles.

    B
    BrianToussaint19-TanzaniteAuthor
    19-Tanzanite
    July 15, 2022

    The problem was that I had forgotten to loop link the route to a conditional.

    D
    18-Opal
    d_graham18-Opal
    18-Opal
    July 18, 2022

    There is a way to restart an existing terminated workflow.

     

    I know this thread has a Solution Accepted but wanted people to know you can backup a process using the technique below.

     

    This technique could also be used to restart a workflow anywhere you want in the process.

     

    The upside of restarting an existing workflow of course is that you keep all the workflow info that has been already stored (with the exception of data that is stored in the Work Item) and you pick up the workflow right where you were when it was terminated.

     

    I made a test workflow and terminated it from the OOTB Process Manager.

    Before Terminate

    d_graham_0-1657985803526.png

     

    After Terminate

    d_graham_1-1657985803585.png

     

     

     

    I then wrote and ran some code in a Windchill shell to restart where it was when terminated but I could have just as easily started it up

    anywhere in the process.

     

    After Restart

    d_graham_2-1657985803514.png

     

     

     

    Note the Start Time is the same in all images.

    Where as this is suppose to correct an inadvertent termination I decided not to update the workflow's original Start Time. Although updating Start Time is doable.

    Note the End Time is updated in the images.  

     

    Note that the Expression and Synch robots were also terminated and restarted.

     

    So, the long and the short of this is it's doable.

     

    David

    Terms & ConditionsCookie settingsAccessibility statement