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

pxCoveredCountOpen does not decrease when agent closes case



A configuration creates parent case and several sub cases. These sub cases are processed and resolved by an agent, so they end up as Resolved-Completed but the pxCoveredCountOpen on corresponding Parent is not 0, it is a positive number, such as 1 or 2.
The conclusion is that the parent case is not automatically closed because the 'AllCoveredResolved' ticket is not raised.
The behavior is sporadic. It seems that the Work-.Resolve activity is executed but only resolves the case and does not decrease pxCoveredCountOpen value.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a Parent case with multiple children
  2. Create a custom agent running on both nodes to process child cases
  3. At some point, all child cases will be closed but Parent has an incorrect pxCoveredCountOpen.

Root Cause

When an agent is processing a Covered case, the lock on the associated Cover will not be taken by default. Hence, depending on the configuration, the system can process the child without updating the parent.


On the very first steps of the activity triggered by the agent, an “Obj-Open-By-Handle” method was used to open the Cover case to get important information but without the lock.
As a local-change, obtain the lock on the Parent before processing the Child to ensure a correct value for pxCoveredCountOpen later.

Published January 31, 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