Clarity PPM1

Expand all | Collapse all

Process step post-condition stuck - Ready to evaluate post condition status, even after action item had finished

Jump to Best Answer
  • 1.  Process step post-condition stuck - Ready to evaluate post condition status, even after action item had finished

    Posted 01-17-2016 04:09 PM

    Greetings.

     

    CA PPM on demand version: 14.3.0.298

     

    We have a process that is "stuck" in a manual action step.

    The status is "Ready to evaluate post-condition", but the approver who received the action item had already approved.

     

    Process stuck.jpg

     

    On the process step details page, we can see that the action item has status "Done", but in the General tab the attribute "Finish Date" is blank.

     

    Process stuck - Action item.jpg

     

    It seems that this process is "stuck".

     

    I have checked the post condition step in the process definition, and if just one approver approves, the post-condition should had been attended.

     

    This problem does not occur in other processes.

     

    What can I do is this situation?

     

     

    Thank you.



  • 2.  Re: Process step post-condition stuck - Ready to evaluate post condition status, even after action item had finished
    Best Answer

    Posted 02-09-2016 05:38 PM

    Hello,

     

    A few things to check:

     

    1. Anything odd in the bg-ca logs?

    2. Is this the only process instance that is stuck? Or are there other instances. If there are others, you may want to check the post condition pipeline.

    3 In general, is the process engine loaded with many errored and aborted processes? See the link below to for best practices for process engine cleanup CA Clarity Tuesday Tips - Process Maintenance

     

    Thank you,

    Ruchika



  • 3.  Re: Process step post-condition stuck - Ready to evaluate post condition status, even after action item had finished

    Posted 02-28-2016 08:08 AM

    Thank you Ruchika.

    You were right about post condition pipeline. After all, we had to increase the pipeline threads.

    But first, we had to open a support ticket requesting restart de BG Service. After BG restart, all process began to work again.

     

    Regards,

    Antonio Matheus A. Tinoco