Support Article

Validation Errors on pyMaxOpenRules while saving operator record



Whenever the user is trying to update and/or save an existing operator after upgrade, Validation errors are been thrown.

When the user tries to create a new operator record, update and save it, there are no errors on it.

The issue occurs only for operators that are involved in the upgrade.

Error Messages

Steps to Reproduce

1. Open an existing operator Id after upgrade.
2. Click Save.

Root Cause

During migration, the blob data for pyMaxOpenRules somehow got corrupted and looks for value as "50" instead of "20" in the upgraded environment and hence are the DictionaryValidation errors on saving the operator.


Perform the following local-change:

1. Since the issue is encountered after upgrade, performing "Revalidate and Save" would regenerate the code for the effected rules.

2. As the first step didn't resolve the issue because the blob data is corrupted, user is suggested to perform the below steps which updates the value of pyMaxOpenRules for operator records.

The above steps open each of the operator record and does a Property-remove of pyMaxOpenRules to remove the corrupted value from blob.

Later when the operator record is saved, it gets saved with the pyMaxOpenRules value as "20" that resolves the issue without any ValidationErrors.

Published May 5, 2017 - Updated May 22, 2017

Have a question? Get answers now.

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