Question
BlueRose Technologies
NL
Last activity: 25 Jan 2017 9:04 EST
Error while processing the work object after SLA executes.
Hi,
I am facing issue while processing the work object. After SLA executes(goal time reached), after that we are using pyContinueAfterWait flow action to automatically process the Work Object but I am getting the "com.pega.pegarules.pub.PRAppRuntimeException: Caused by Save, Delete or Commit has failed" error.
We are using Pega 7.1.9
Please find the attached file for full information.
Any who knows about this issue .Please suggest.
***Moderator Edit: Vidyaranjan | Updated Categories***
Pegasystems Inc.
IN
The error suggests locking related issue. Could you trace the SLA agent with Locking event enabled and see why lock is getting released and attach the trace xml here?
Also let us know what kind of locking mechanism is being used by this case.
BlueRose Technologies
NL
Hi,
We are not able to trace the SLA agent. Due to security reasons tracer through SMA is not enabled and we are using default case locking.
Pegasystems Inc.
IN
Could you check if the below article describes your scenario and if it helps.
https://community.pega.com/support/support-articles/advance-flow-does-not-work-subcase
If not, Could you let us know your exact configuration ?
Is there any processing activity which is doing commit ?
BlueRose Technologies
NL
We are not having any parent child relationship between work objects. Its only single WO.
We are using pega marketing over here, so in that whenever a campaign executes its saves the information in a external database table. At that external table we are having our agent configured to process the information. After agent executes, we are initiating our flow to create the WO. Our flow is a straight through process.In the flow we are connecting with a end system, if that endsystem is down, we are sending the WO to a work basket. At that workbasket we are waiting for 5 mins and as soon as goal time is reached we are using pyContinueAfterWait Flowaction to process the WO. But after the Goal time is over, SLA executes and it tries to process the WO. This error is coming.