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

Service Registry does not consider node if hearbeat not updated



The Service Registry does not consider a Service node, if the node has not updated its heartbeat for more than 90 seconds. However, these stale services are removed from the database later. If the heartbeat takes longer than its beat to update services, then the hearbeat must display a thread dump at that moment to determine where it has stopped.

Error Messages

Not Applicable

Steps to Reproduce

Not Applicable 

Root Cause

A defect in Pegasystems’ code or rules.
Some platform components do not use the Service Registry API correctly, causing the heartbeat to slow down. As a result, the node becomes unhealthy.


This feature is implemented in Pega Platform 8.3.4.
Suggest Edit

Published December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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