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

AES sends Node Unavailable notifications



User has upgraded to Autonomic Event Services (AES) 7.3 on Pega 7.4 monitoring production Pega 7.2 environments. Post this upgrade, AES sends Node Unavailable notifications while nodes are running correctly.

Error Messages

Not Applicable

Steps to Reproduce

Not Applicable

Root Cause

This behavior is as per Pega product design.


Here's the explanation for the reported behavior:

AES remote agents running in monitoring nodes send Health Message to AES every two minutes. If the agents are busy with other activities or with a large processing, Health Messages are not sent to AES. Hence, AES displays the Node Unavailable alert.


Published December 19, 2018 - Updated December 2, 2021

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