Support Article

Rule checkout fail

SA-12244

Summary



You try to check out a flow but it displays an error stating that it is locked, however no checkouts exist.


Error Messages



Check out failed. Original record already locked by <operator> on <datetimestamp in EDT>

Steps to Reproduce



Attempt to check out a specific flow rule.

Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules that results in the lock not being releasesed on the Rule-File-Binary instance associated with the flow.  This can also result in the Rule-File-Binary persisting to the database in a corrupt state.

Resolution



This issue is resolved through the following local change: 

First, follow the instructions in SA-2534 to release the lock on the Rule-File-Binary instance.
 

This issue is resolved by searching for the binary rules with 'OLD:' keyword which searches using previously indexed data at database level and releasing the lock on those rules by clicking on Action>Release Lock.
 

After confirming that the flow can be checked out, test checking it in again.  If the following error is encountered:
 
The Flow Action post-processing activity PostActionCheckin failed: RulesetName is not specified

You can avoid this secondary error by saving the flow into another ruleset, deleting it from the original ruleset, and then copying it back to the original ruleset.


 
Suggest Edit

Published July 20, 2015 - Updated October 8, 2020


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.