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-Message error appears intermittently



After calling a SOAP connector, the application can not open the correct instance of Rule-Message for a class.

Error Messages

"Attempting to access a rule with a bad defined-on class."

Steps to Reproduce

Create a Connect-SOAP rule. Execute it multiple times, this will eventually occur.

Root Cause

The message-reporting logic in the alert layer was missing the pxObjClass of a Rule-Message, which caused the error.


Apply HFIX-26145

Published March 18, 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