Discussion

Error: Assignment Mismatch

Hi

We have a requirement where work objects are to be transferred from a work basket to different user work lists. We are currently calling the Work-.Reassign activity from a custom activity to transfer the work objects to different user work lists. When these work objects are opened from the work lists we get an Assignment Mismatch error- "The work object references a different assignment than the current one". However this does not happen for all the cases most work objects open correctly. I read the Troubleshooting-Error:Assignment Mismatch article but it is not very useful. We are not able to identify the problem as the error is not consistent , 3-4 cases out of 10 shows this error.

Could you please help in this regard. Is there anything that i can do differently?

**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.

Comments

Keep up to date on this post and subscribe to comments

Pega
June 25, 2009 - 10:52am

I'd look at your custom activity that calls Reassign. It is potentially undoing some of the settings in Reassign, particularly the part where the work object's pxFlow page is updated.

November 13, 2012 - 3:14pm

I have the same issue.....users report this occurring once every few days....and I have not be able to duplicate....

November 13, 2012 - 3:14pm

I have the same issue.....users report this occurring once every few days....and I have not be able to duplicate....

September 12, 2013 - 4:12am

Hi, Could you please let us know if you ended up on any solution for this issue. I also face this issue while transferring case from WB to WL. Also we have a commit statement right after the call to Reassign activity.

Pega
October 9, 2013 - 7:35am

Most of the time, these issues come due to explicit commits by customer. You should not be using any explicit commits.

 

Explicit use of the Commit method can cause data integrity issues. Flow processing already manages the boundaries of work-related database transactions and adding commits can create synchronization problems between what is assumed to be in the database and what actually is in the database. This situation can make it extremely difficult to track bugs and cause data integrity issues. Additionally, object locks are often released upon the commits, which can make it even more difficult to track and recreate data integrity issues.

 

Transaction boundaries in the flow are at:

 

  • Flow Start shape
  • Each assignment shape
  • Flow End shape

 

These are the points at which PRPC will automatically take care of “Commits”

 

January 29, 2014 - 9:30am

Hi Nishant
Can you please tell possible solutions to fix assignment processing error,you have told possible scenario on forum.Also if you can share possible scenario of assignment not getting removed and solution to fix it ,would be helpful.

Thanks.

Pega
January 30, 2014 - 12:40am

Pega by default provides ways to fix beoken assignments. That would generally involve deleting the assignment or restarting the flow altogether. You may see the recommended options under Pega(button) > Process and Rules > Tiiks > WorkAdmin > 

 

You can see diferent kind of errors and PRPC will give you option to repair it.

February 5, 2014 - 12:59pm

 

SwitchToWorkbasket is the property you need to set it to false before reassigning to worklist.

For more information look at "AddAssign" activity in "Assign-Worklist"

July 22, 2015 - 9:18am

Hi,

I am getting below error.

"The work object references a different assignment than the current one". When i open Wo it is saying "Repair the assignment".  I have create 30 cases, getting the same error.  Please help me out.

 

July 24, 2015 - 12:57am

GopalaraoP - Observe the flow metadata in the case. Watch pxflow and the lastassignment data.Trace adn see whats happening. Also let ur version of prpc ?

 

Thanks,

Ashok

August 9, 2015 - 9:20pm

These issues will happen in one of the below scenarios

1. Custome logic written(Reassign...etc) where there is a discrepancy in the pxFlows of the work object and the assignment. Ex:- If we have written a custom activity to resolve a case(although not recommended) and if we are deleting the actual assignment(Assign-WorkList or Assign-Workbasket) but has not updated the pxFlow. In this case any SLA rule defined on the assignment tries to work on the pxFlow and causes this error. I have taken the example for removal this can be the case for completion of the assignment as well.

 

2. As one of our member in the above trail mentioned, another reason would be using explicit commits in between the activities.

 

 

September 11, 2015 - 6:59pm

Does anyone have solution on this? We are facing same issue for all the assignments that are being transferred from Workbasket to user's work list.

October 28, 2015 - 10:41am

Please provide the solution, we are also facing same issue.

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" .

 

October 28, 2015 - 12:20pm

Hi Ravi 

Have a look at the PDN article : https://pdn.pega.com/process/troubleshooting-errorassign-mismatch-when-a-before-this-action-activity-transfers-a-work-object

This should resolve your issue.

 

Regards

October 29, 2015 - 6:04am

Hi Bhavya,

Thanks for the quick response.

We are calling the reassign activity in the flow action post activity as mentioned in the provided article.

But still 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". 

Regards

 

November 19, 2015 - 1:24pm

I have also had the same issue in my current project when email interaction case picked up from the workbasket where it was originally created by listener. There is a reassign happens to assign the case to his work list when user pics upthe email interaciton case from the workbasekt. In this process the assignment record will be updated correctly to reflect in user worklist but the pxflow page was not updated correctly and still the assignment key was pointed to "Assign-Workbasket XXXX". To get rid of this issue, I have Used a dummy flow action (at the first assignment routes to workbasket) with hiding the default buttons and call the "ActionAutoSubmit" section. Have the another assignment routes to current operator connected to the dummy flow action.

May 6, 2016 - 8:02am

Ashok_Bommisetty sayd: "Watch pxflow and the lastassignment data..." - That helped. In the customized "Reassign" activity  I've added the step with Obj-Save method to save work object. So, now we can transfer assignments between WorkList and Workbasket both ways;  the "Error: Assign Mismatch" is not reproduced