Question

Error: Assign Mismatch

While assigning Assignment to worklist from workbasket we are facing issue like instance is removing from assign_workbasket and inserting in to assign_worklist table with PYASSIGNMENTSTATUS as "Error: Assign Mismatch" , I have checked all recent and old posts but its not use full, We are getting this only for fue case.

Its not updating the pxFlow in clipboard ,In pxFlow it is still pxAssignClass->Assign-WorkBasket

In newAssignPage --pxAssignClass->Assign-Worklist only

Please help me with this issue

Comments

Keep up to date on this post and subscribe to comments

August 14, 2019 - 8:48am

What Pega version are you using?

What flow actions and activities are you using for transferring from the workbasket to the worklist? Are these OOTB or customized?

Do you have any SLAs or agent activities that could be trying to run at the same time?

August 28, 2019 - 3:47am
Response to CarissaW_GCS

We are using Pega 7.2.2 and yes we are using customized activity for transferring.

No except Overall SLA nothing is there

 

August 28, 2019 - 6:41am
Response to DoddaN04

In your custom activity, do you only use deferred deletes and saves and then commit both the assignment data and work page data at the same time at the end? If immediate deletes and saves are used for the assignment and the work page is committed later, then a failure in saving the work page would cause the work page data to roll back and be out of sync with the current assignment data already committed.

August 15, 2019 - 10:10am

Hi

Please refer to the links below in order to get some insights. AS pointed out by Carissa, it would be helpful if you can list down the steps you are following to reassign the case from WB to WL.

https://community1.pega.com/community/product-support/question/assignmismatch-errors-happening-when-case-transferred-workbasket

https://community1.pega.com/community/pega-product-support/question/error-assignment-mismatch

August 28, 2019 - 3:57am
Response to AnoojitD

already I saw these post, its no helpful for my issue, we followed as mentioned in the Link still we are getting this error message for only few cases not all cases and we tried to reproduce in lower env's also but we are not getting this error msg in lowe env's