Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Error while reassigning a case



When case is reassigned to another user an error is reported.

Error Messages

Error in Logs :
2015-09-03 18:48:40,618 INFO [STDOUT] 2015-09-03 18:48:40,618 [] [TABTHREAD4] [ ] ( mgmt.base.ThreadUITransaction) ERROR | UserID - ERROR: posted transaction id '6c3ead8f891bea39e13a850e739b970b' for frame 'pyWorkPage' DOES NOT match record '02e9ae8cf7b3c15252b3636324440adc'

Steps to Reproduce

Reassign case to another user and check for error message.

Root Cause

FinishAssignment is being called after Reassignment and generates two different transaction ID’s. Transaction ID's don't match.


Expected behaviour when FinishAssignment was called after the reassignment in an Activity in PRPC 6.2 SP2 

Resolved in PRPC 6.2 by SP2 the reassignment of work objects performed without the
FinishAssignment to avoid creation of second Transaction ID.

Resolved in PRPC v7.1.x by means of an UI Action List.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us