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

System throwing BADCLASSDEF error when it encounters an alert



BADCLASSDEF error occurred when it encounters any alert message. User is facing this issue when trying to connect to an external system.

Error Messages

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

Steps to Reproduce

Perform a SOAP integration call, which exceeds one second.

Root Cause

Within the module, the doAlert method does not have pyClassName key when it opens the Rule-Message instance for the alert string.


Apply HFix-28362.

Published February 10, 2017 - 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