Support Article

Flow wait shape followed by utility stops processing

SA-28370

Summary



User has a Flow with 4 shapes:
 
  1. Start
  2. Wait (set to timer = 1 minute)
  3. Utility (with an activity which uses Data-Decision-DDF-RunOptions.pxRunDDFWithProgressPage to start a data flow
  4. End which sets status to resolved-completed.The data flow is started properly by the activity, but then the work item created by running the flow seems to stop at the connector between the utility and the stop shape, the final entry in the audit: 


Assignment to ' Await Date/Time ' completed by performing a 'pyContinueAfterWait'. 

This seems to be specific to the combination of wait followed by starting a data flow.

Error Messages



com.pega.pegarules.pub.PRAppRuntimeException: Caused by Save, Delete or Commit has failed because lock "ABC-XYZ-WORK P-106" is not held
 

Steps to Reproduce

Create a Flow with four shapes : 

  1.  Start 
  2.  Wait (set to timer = 1 minute) 
  3.  Utility (with an activity which uses Data-Decision-DDF-RunOptions.pxRunDDFWithProgressPage to start a data flow 
  4. End which sets status to resolved-completed.


Root Cause



This is by design of the Data flow that before its execution it triggers a database commit. Due to this commit the earlier lock on the main Flow is lost.
Thus after execution of the Data Flow the control cannot resume the mai flow due to lost lock.

Resolution

Instead of using Wait shape an utility activity calling wait method is a viable alternative.

Published September 23, 2016 - Updated September 29, 2016


0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.