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

Errors occur sporadically on click of Next button in a section



On click of Next button in a section, transaction ID mismatch errors occur sporadically.

Error Messages

ERROR: posted transaction id 'xxxxxx' for frame 'pyWorkPage' DOES NOT match record 'xxxxxxxx'

Steps to Reproduce

Click the Next button to submit a screen.

Root Cause

An issue in the custom application code or rules. An explicit commit in a custom activity changed the transaction ID.


Perform the following local-change:

For work object and assignment data, allow normal flow processing to handle saves and commits. For other data, if there is an explicit need to save and commit the data outside of flow processing, use an Obj-Save with write-now to prevent the transaction ID from changing.


Published July 26, 2018 - 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