Close popover
Jahnavi Paladara (JahnaviP)

JahnaviP Member since 2015 3 posts
Posted: November 11, 2018
Last activity: April 3, 2019

Broken SLA and Error Assignments


In 7.1.8 version of PRPC, we have a case type, where we are using "Delete open assignments upon resolution" setting at resolution stages. Few Resolved cases have error assignments remained in the pc_assign_worklist which have to be removed at the time of resolution according to the setting. The assignment errors are

1. "ProblemAssignment_FlowRemoved" - My understanding of this error messages is, the assignment is not removed because its associated flow is deleted by that time. Here my question is which pega rule takes care of pending assignment and flow removal at the time case resolution. Why that is failing sometimes?

2. "The assignment is no longer available". - My understanding of this error message is, when SLA agent processes the SLA item after the assignment is removed - but still assignment is available in worklist in error state. Here my question is, how come the assignment is restored in the worklist when it was not available while SLA was processed?

And the SLA items associated with such error assignments are in "Broken-Process" state. Logs don't have any information.

Is my understanding of the error messages correct ? Could you let me know, what scenarios could cause such exceptions and how could i replicate those. I created multiple test cases, none of them returned these errors. And as these errors are intermittent, i was unable to understand the use case which is causing such exceptions.

Thanks and Regards

Case Management
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.