We are using Pega 7.1. for example the rule is in 02-94-01 version in RSMIAC ruleset. But it is hitting earlier version rule. We see the the RSMIAC: 02-94 is referred in application. No Clue whats happening
How many nodes in the environment? Is the system pulse running? we have 2 nodes and system pulse running perfectly fine.
Does the issue only occur for certain types of rules? For example, do you see the issue with stream rules, activities, when rules, etc.
yes it occurs with Activities
Does the issue occur when migrating to another environment? Yes when we migrate the code from Dev to UAT. We have 2 nodes in UAT. one 1 batch node 4807 and another one is realtime node is 4810. In both the node an activity in the lower version is getting hit when the user invokes a flow from Front end application.
Going forward, you should NOT truncate cache tables. I know this has been given as a thing to do in earlier releases, but with the introduction of the VTable cache in the 7 series, except in certain exceptional circumstances, you should not be truncating entire cache tables.
It is likely you have encountered a known error when you did the import (said error not existing in the 7.2 series). In order to avoid future occurrences of this error, please make the following change in your prconfig file; the change will take effect the next time you start the JVM. (Doing this via the DSS path will still require a restart of the JVM to take effect.) This will introduce a 60 second delay between the time you import on one node and the time the system pulse processes the new entry after moving it onto the other nodes. The technical reason why this works is complicated; you will have no performance impact by the change.
Set "systempulse/scanoffsetms" to 60000
In order to fix the problem you currently have, use the SMA to connect to the node on which you have the problem and use the VTable Cache tool (Virtual Rule Table Cache Management) to remove the existing entries for the bad rule from first the database, and then memory (two different buttons). You will need to open the XML of the rule in question in order to provide the required fields -- be careful not to mis-type.
Could you please give a tag to set systempulse/scanoffsetms" to 60000 in prconfig file.
Also in VT Table management under Advanced in SMA, Do we have to give the objclass and instance name of the particular rule to remove the Database and memory cache?
This usually happens when we promote/migrate our code from Dev to UAT. Do we have to always restart the server upon deployment. Because we usually see this getting resolved after restarting the server. But we really not required to restart correct after deployment.
Is it the same activity on both nodes that is getting missed? OR is it a different activity on each node?
I'm not familiar with 7.2 to the degree I would like. Can you use the SMA to examine the VTable entries for the activity(activities) of interest and clear both the memory and database VTable entries for same? Clear Database first and memory second, as otherwise the memory might get refreshed from the bad database cache entry. Does the problem then go away?