Question1Replies136Views chars1 Member since 2015 46 posts PEGA Posted: March 15, 2016Last activity: March 16, 2016 Closed SystemPulse does not work on 717 (upgraded from 6.3)Hi there,My client was on PRPC 6.3 last year and moved to to 717. I noticed that two tables with triggers used to update pr_sys_updatescache.Question - does the triggers still used for SystemPulse update?, I have seen a discussion somewhere that it is not used. if1. dbo.pr4_rule has 3 triggers (trpr4_rule, trp4_rule_vw_del, trp4_vw_upd) - the triggers in dbo has no schema prefix - insert into pr_sys_updatescache 2. rules.pr4_rule also has the tree triggers (but the insert has schema "rules" prefix ie. insert into rules.pr_sys_updatescacheI think 717 upgrade back then also introduced split schema - I notice no new rules in dbo.pr4_rule_vw but most recent rules with pyCreateDatetime are in rules.pr4_rule_vw1. I can see the dbo.pr_sys_updatescache table has the most recent rules... 2. the SystemPulse agent is running on both nodes3. the Pulse Status also shows the same activities in the last 1 hour seen by botn nodes.What should I check to see why the both nodes are not in synch?RegardsSeri System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 4 years agoKevinZheng_GCS PEGA replied to chars1see this link: Re: Changes in one node is not reflected in another and the articles in it.