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

Advance flow does not work on subcase



A subcase experiences errors when the SLA performs an Advance Flow and there is a dependency between parent and child.

Error Messages Caused by Save, Delete or Commit has failed because lock "A-B-C W-1" is not held From: (Requestor ID).

Steps to Reproduce

1. Create a child case under a parent case.
2. Define dependency on the child case in the parent case.
3. Define an SLA to move the child case to the dependency status.
4. Observe that the SLA throws an error stating that lock is gone.

Root Cause

The root cause of this problem is a defect in Pegasystems code. For flow dependency and wait shape processing an activity is called named “pxCheckFlowDependencies”. When a dependency is reached and the currently logged in operator has a different access group than that of the operator who initiated the wait shape, the activity “pzSpawnQueueItemForFlowDependency” is called. When the activity “pzSpawnQueueItemForFlowDependency” is called, it has a commit at step 8, which cause the lock on the current open case to be released and does not regenerate the lock. This causes the lock lost failures for any further processing.


This issue is resolved by HFix-21542.
Suggest Edit

Published July 22, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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