Discussion
TATA Consultancy Services Ltd
IN
Last activity: 4 Oct 2018 11:08 EDT
Wait Shape to Assignment - Error: Agent SLA Activity
Error: Agent SLA Activity is coming after the Deadline time reached in Wait Shape. If multiple Wait shape applied consecutively, only the last Wait shape which is connected to an Assignment shape is showing this problem. Rest all are fine.
Options tried for "Assignmnet Type" in the Assignment shape just after the Wait shape are -
- Worklist
- Workbasket
- WorkList with ToWorklist Router
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
TATA Consultancy Services Ltd
IN
The Error Message says -
Save, Delete or Commit has failed because lock "XXX-XXXX-XXXX R-3547" is not held
World Bank
US
Hi Subhasis,
Is this resolved?I am facing same issue .Please let me know if you know the fix
Pegasystems Inc.
IN
Hi SUBHASIS,
Could you please share which PRPC Version you are using and some more detail about the scenario where you are facing the above said problem?
TATA Consultancy Services Ltd
IN
The version is 7.1.2
Viable Solutions
AU
Hi SUBHASIS,
Can you explain this statement ? Agent SLA Activity is coming after the Deadline time reached in Wait Shape.
Also, the issue seems to be with the lock which is not available to system/agent not with wait shape or assignment shape.
Can you provide more details on the process you have mentioned here.. .
Pegasystems Inc.
US
Hi Subhasis,
Mkake sure you provide complete routing configuration to the assignment that is after wait shape. Since the wait shape is progressed by System, the routing oprions like toCurrentOperator does not work. Route the assignment to some user and try.
Pegasystems Inc.
US
Okay, so if you are getting
Save, Delete or Commit has failed because lock "XXX-XXXX-XXXX R-3547" is not held
and
Error: Agent SLA Activity
it means the SLA agent woke up to do processing, but didn't have the lock. This should never happen. You should contact GCS (Pega Support) and have a screenshare so that our experts can get a closer look at your configuration.
AI4Process Ltd
GB
Trace and see where the lock issue is coming and before that step add Obj-Refresh-lock. This will resolve the issue.
Tcs
IN
Hi, we are also facing the same issue "Error: Agent SLA Activity" . But we are getting this when we are calling a AdvanceFlow or activity for service call (when it is failing) in SLA DeadLine.
Can anyone please help me on this?
Tcs
IN
We are using Pega 7.1.8
Pegasystems Inc.
IN
Hi Yuvarani,
Did you try tracing the agent, it should give good insight on what could have gone wrong.
Error:Agent SLA Activity message is very abstract. Having a view of complete stack trace should help strongly.
Thanks,
Ujjwal