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

Bulk Transfer functionality is not working properly



When transferring more than 30 cases from one workbasket to other workbasket with "Run in Background" checked, developer is getting LockGoneException. It appears that the cases are running in the background but not going to the directed destination. They are just running in the background and then reappearing in the original workbasket.

Error Messages Save, Delete or Commit has failed because lock "X-X-X" is not held 

Steps to Reproduce

Transfer multiple cases from one workbasket to another workbasket. 

Root Cause

There is a custom activity which performs "Obj-Save" to attach a note to the work object. Generally the above error message is because, Obj-save methods requires a lock to save any instance. 



Include a step which performs "Obj-Refresh-Lock" before "Obj-Save" which makes sure that the lock is held on the Work Object before writing it to the database.

Published May 25, 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