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

GetNext-MoveToWorklist does not honor Optimistic Locking



When using the  GetNextWork (GNW) with Optimistic locking to fetch an assignment, the work object is locked and is not released. Additionally, when a different user opens the same assignment and submits it, error occurs.

Error Messages

Assignment is already locked by other user
Lost ability to make change

Steps to Reproduce

  1. Create a case type with Optimistic Locking.
  2. Set GetNextWork_MoveAssignmentToWorklist to false in the local ruleset.
  3. Create some cases and open the first case from work basket.
  4. Click GetNext. The second case acquires a lock. Hence, users cannot submit the case. Step 5 of MoveToWorklist activity has a precondition which jumps to Step 17 on false. Step 15 and 16 are related to checking Optimistic Locking.

Root Cause

A defect in Pegasystems’ code or rules.


Apply HFix-59588.

Published January 16, 2020 - 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