VMware vRealize Orchestrator nodes update their heartbeat in the database every 5 seconds. The default number of missed heartbeats that indicates a problem on a node is 3 heartbeats.
If a vRealize Orchestrator node has a problem and stops the heartbeat, vRealize Orchestrator is aware that its heartbeat has stopped. When the heartbeat entry in the database is not updated, other vRealize Orchestrator nodes in the cluster will know that the heartbeat of the node with a problem has stopped.
When the timeout is reached, the following happens:
The vRealize Orchestrator node with the problem disappears from the Started Cluster Nodes section under the Server Availability option in the Orchestrator configuration page
The other vRealize Orchestrator nodes in the cluster determine that it is nonresponsive and take over the workflows
Once the server is ready to be brought online after fixing the issue, it's recommended to restart the impacted Orchestrator...