Support Article
System Pulse is not working properly in some nodes
Summary
System Pulse is not working Properly in some nodes and user is getting below error.Error Messages
Agent Pega-RULES #1: Code-.SystemPulse encountered an execution error.
Restarting after delay.
Exception at 20160808T053013.924 GMT:
com.pega.pegarules.pub.PRRuntimeError: Pulse processing is skipped on this node because this Node status is set to 'UNKNOWN'.
at com.pegarules.generated.activity.ra_action_systempulse_4c6ed01c400db07b3258cad866df6542.step1_circum0(ra_action_systempulse_4c6ed01c400db07b3258cad866df6542.java:504)
at com.pegarules.generated.activity.ra_action_systempulse_4c6ed01c400db07b3258cad866df6542.perform(ra_action_systempulse_4c6ed01c400db07b3258cad866df6542.java:69)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375) at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:719)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:600) at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:913)
Steps to Reproduce
Not ApplicableRoot Cause
System Pulse processing is skipped on this node because this Node status is set to 'UNKNOWN'".
Above error trace tells that system pulse activity simply runs the step 1 and exit the activity. Resolution
Apply HFix-25642, which ensures that the system is in consistent state after starting up.
Published August 30, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.