Is there a known Pege Defect in which SLA agent saves an assignment back into assignment table after the WO is resolved by user, and the assignment is deleted from assignment table? This causes dangling assignment, i.e. WO resolved and flow removed, but assignment remains.
I doubt this is what happens in our 6.2 SP2 production environment. In our SLA rule definition, no escalation activity is defined. And SLA agent and user are trying to work on the WO at the same time.
***Updated by moderator: Lochan to add Categories***
Thank you very much for answering! The issue that you mentioned is very likely what has happened in our production environment. Does Pega provide hot fix for it? Carissa mentioned HFix-7745 in 6.2 SP2, does it address the issue that you mentioned?
Posted: 5 years ago
Posted: 27 Jul 2016 8:43 EDT
Carissa Wenhardt (CarissaW_GCS)
Principal Software Solutions Engineer
I am not sure about the assignment being put back but I have seen cases where Flow Removed errors have occurred due to a user and SLA agent trying to process an item at the same time. HFix-7745 addresses that scenario in 6.2 SP2 so you could see if that helps.
I am facing the same error. I can see a work object is Resolved-Completed in production. The status of assignment is also Resolved-Completed but still the assignment is in WorkBasket. How shall I delete it?