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

Rule Resolution Issue After Code Deployment



After deploying a new code in Production, duplicate rules display. The duplicates have nearly-identical pzInsKeys with only the timestamps differing by a few milliseconds

For example, 



Error Messages

PEGA Logger com.pega.pegarules.exec.external.basic.conclusions.AbstractClassResolvableConclusion throws a Warning message in the logs that rule resolution can't find the rule.

[ttp-nio-8443-exec-20] [TABTHREAD2] [ ] [FinoColWB:01.02.01] (tractClassResolvableConclusion) WARN| JJones - Rule Resolution should have returned a single rule, but 2 rules were returned

Steps to Reproduce

Send mail through a local flow action.

Root Cause

A defect in Pegasystems’ code or rules. 
Two users or agents can work on the same item within a few milliseconds and each process will create a new rule. 
If the operation is to create a  new copy of a rule, then both the copies are created with slightly different timestamps in the pzInsKey.


Perform the following local-change to prevent two users or agents from working on the same item at the same time:

Add the below prconfig setting:

<env name="/database/maxlockattempts" value="1"/>

Published August 15, 2019 - 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