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: posted transaction ID for frame DOES NOT match record



Transaction ID mismatch errors appear.

Error Messages

posted transaction id 'a1d4d8402383e716aead0d23b081361f' for frame 'pyWorkPage' DOES NOT match record '6a799f21a213921a73839f98653314ea'

Steps to Reproduce

  1. Create multiple tabs focusing on different work objects. Each tab will be on a separate thread and will have its own pzTransactionID. The tab should not refresh when it is active as a result of a user click on the already existing tab.
  2. Have a button present in each tab, which runs an activity that returns no content.
  3. Switch from one tab to another tab.
  4. Click the button, which fires the activity. 
  5. Perform any other action on that tab, which performs a POST, like reloading a section.

Root Cause

A defect in Pegasystems’ code or rules:
Executing the activity that returns no content replaces the pzTransactionID of the current thread by the pzTransactionID of the previous thread.


Apply HFix-29263.

Published September 21, 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