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

pyCommitError on trying to open the work object



User has configured the use case and when trying to use the work object that was just created, it gives below error.

Error Messages

The deferred save failed with the following exception Save, Delete or Commit has failed because lock "PEGACRM-ENTITY-CONTACT CON-20683" is not held

Steps to Reproduce

1. Create a work object.
2. Try using the same work object in other flow.

Root Cause

User has configured consecutive activities with deferred Saves and then trying to perform an Obj-Save with commit in one of the steps in the later invoked activities.

Soon after this step, they have another activity with does Obj-Save on the same context.

Because of which the deferred Saves are failing.

Use of Write-Now option interferes with PRPC commit transactional model and cause stale records of database.

And since that there are already other deferred saves that are available in queue, having Write-Now would not allow to commit those changes to db since the one with Write-Now has already committed to the DB with stale records.


User is suggested to uncheck "Write-Now" from Obj-Save step as a best practice which resolves the issue.

Published May 24, 2017 - 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